[
https://issues.apache.org/jira/browse/MUSE-208?page=com.atla
ssian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Jemiolo closed MUSE-208.
----------------------------
Resolution: Fixed
Applied Alberto's patch
> 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
> Assignee: Andrew Eberbach
> Priority: Minor
> Fix For: 2.3.0
>
> Attachments: Messages.properties.diff,
ResourceInspector.java, ResourceInspector.java.diff
>
>
> 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
|