[
https://issues.apache.org/jira/browse/AXIS2-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645493#action_12645493
]
daniel.golesny edited comment on AXIS2-813 at 11/6/08 8:05 AM:
---------------------------------------------------------------
Hi Guys,
I tried this "fix" with Axis2 1.4.1 (Tomcat 6.0.18, jdk 1.5.0_11-b03) (should
be fix in there, not?), but there is the same problem, even with the original
attachment "AddressManager".
Here is the part of the wsdl:
<xs:complexType name="AddressManager_Address">
<xs:sequence/>
</xs:complexType>
Please reopen this bug!
I'll attach a simplier example with aar and client for a fast check.
Edit: This is very strange, after I commited this request, I collect the files
to attach and tried the aar again. Now I can see the complex datatype:
<xs:schema attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="http://v1_0_0.ws.gen/xsd";>
<xs:complexType name="EchoPojo2_EchoPojoInner">
<xs:sequence>
<xs:element minOccurs="0" name="echoString" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
But only my aar, the AddressManager-WSDL still does not contain the complex
type.
But my echo-client, nor the server, sent null for the member "echoString". So,
test the client and you'll get an null in both directions.
Very strange is the behaviour that the "?wsdl" generates the wsdl, but the
"?xsd" result in follwoing error (perhaps this has nothing to to with it):
<soapenv:Reason>
<soapenv:Text xml:lang="en-US">
The service cannot be found for the endpoint reference (EPR) /axis2/services/
</soapenv:Text>
</soapenv:Reason>
But the version-service can generate the xsd!
Regards,
Daniel
was (Author: daniel.golesny):
Hi Guys,
I tried this "fix" with Axis2 1.4.1 (Tomcat 6.0.18, jdk 1.5.0_11-b03) (should
be fix in there, not?), but there is the same problem, even with the original
attachment "AddressManager".
Here is the part of the wsdl:
<xs:complexType name="AddressManager_Address">
<xs:sequence/>
</xs:complexType>
Please reopen this bug!
I'll attach a simplier example with aar and client for a fast check.
Edit: This is very strange, after I commited this request, I collect the files
to attach and tried the aar again. Now I can see the complex datatype:
<xs:schema attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="http://v1_0_0.ws.gen/xsd";>
<xs:complexType name="EchoPojo2_EchoPojoInner">
<xs:sequence>
<xs:element minOccurs="0" name="echoString" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
But the client, nor the server, sent anything back but null. So, test the
client and you'll get an null in both directions.
Very strange is the behaviour that the "?wsdl" generates the wsdl, but the
"?xsd" result in follwoing error (perhaps this has nothing to to with it):
<soapenv:Reason>
<soapenv:Text xml:lang="en-US">
The service cannot be found for the endpoint reference (EPR) /axis2/services/
</soapenv:Text>
</soapenv:Reason>
But the version-service can generate the xsd!
Regards,
Daniel
> Automatically generated WSDL fails to generate complex type for inner classes
> -----------------------------------------------------------------------------
>
> Key: AXIS2-813
> URL: https://issues.apache.org/jira/browse/AXIS2-813
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: wsdl
> Reporter: Jochen Wiedmann
> Assignee: Deepal Jayasinghe
> Priority: Minor
> Attachments: AxisInnerClassesBug.tar.gz, example.zip,
> SchemaGenerator.diff
>
>
> I have created a class "AddressManager", which uses an inner class "Address".
> The inner class is used as a parameter and result type in "AddressManager".
> As a next step, I have created a "services.xml", in order to make the
> "AddressManager" available as a web service. I followed the descriptions in
> the section on "Use Axis2's primary interfaces (APIs) and implement the
> business logic." from userguide2.html.
> Deploying this web service works fine. The automatically generated WSDL looks
> good at first glance. However, closer inspection shows that the complexType,
> which is created for "Address" doesn't contain any elements, or attributes.
> This is caused by the fact that "Address" is an inner class: If you refactor
> the inner class as an outer class, then everything works fine.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
