You are viewing a plain text version of this content. The canonical link for it is here.
Posted to muse-dev@ws.apache.org by "Dan Jemiolo (JIRA)" <ji...@apache.org> on 2007/03/17 19:16:09 UTC
[jira] Assigned: (MUSE-208) Use WSDL operation name instead of XSD
element name during code generation
[ https://issues.apache.org/jira/browse/MUSE-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Jemiolo reassigned MUSE-208:
--------------------------------
Assignee: Andrew Eberbach (was: Dan Jemiolo)
> Use WSDL operation name instead of XSD element name during code generation
> --------------------------------------------------------------------------
>
> Key: MUSE-208
> URL: https://issues.apache.org/jira/browse/MUSE-208
> Project: Muse
> Issue Type: Bug
> Components: Tooling - Code Generation
> Affects Versions: 2.2.0
> Reporter: Saurabh Dravid
> Assigned To: Andrew Eberbach
> Priority: Minor
> Fix For: 2.3.0
>
>
> If I provide the parameters to the operation in the following way, codegeneration didn't generate operation with parameters.
> <xsd:element name="startApp" type="tns:startAppType"/>
> <xsd:complexType name="startAppType">
> <xsd:sequence>
> <xsd:element name="appName" type="xsd:string"/>
> <xsd:element name="port" type="xsd:string"/>
> </xsd:sequence>
> </xsd:complexType>
> Generated Interface class method appears as
> public void startApp();
> But If I moved the type definition as inline like this
> <xsd:element name="startApp">
> <xsd:complexType name="startAppType">
> <xsd:sequence>
> <xsd:element name="appName" type="xsd:string"/>
> <xsd:element name="port" type="xsd:string"/>
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
> Then it generates a proper java method.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org