[ http://issues.apache.org/jira/browse/AXISCPP-898?page=comments#action_12368373 ]
Adrian Dick commented on AXISCPP-898: ------------------------------------- Ok, I think I understand the problem here. The WSDL2Ws tool correctly determines your t_NonNegativeInt is a simple type, due to it's being a derivate of the built-in simple type xsd:integer. However, it incorrectly determines t_Age as a complex type. Looking at the WSDL2Ws code, this is because the WSDL parsing portion hasn't added these to the table of simple types. The first case works because some "special case" logic has already been added to check the immediate parent type. As for a solution, we can either: - Look recursively at the parent types until we can determine correclty. - Alter the parsing code to flag these as simple types and add them to the lookup table. The second option is my preference as it will avoid the need for "special case" code scattered throughout. > simple problem with simpleTypes > ------------------------------- > > Key: AXISCPP-898 > URL: http://issues.apache.org/jira/browse/AXISCPP-898 > Project: Axis-C++ > Type: Bug > Components: Client - Stub > Versions: 1.6 Alpha > Environment: W2KSP4 JDK 1.5.0_06 > Reporter: Franz Fehringer > Attachments: PegsTour.wsdl, PegsTour.xsd > > Given the construct > <xsd:simpleType xmlns="http://www.pegs-pegstour.com/API/XMLSchema/1.0.1"; > name="t_NonNegativeInt"> > <xsd:restriction base="xsd:integer"> > <xsd:minInclusive value="0"/> > <xsd:maxExclusive value="2147483647"/> > </xsd:restriction> > </xsd:simpleType> > <xsd:simpleType xmlns="http://www.pegs-pegstour.com/API/XMLSchema/1.0.1"; > name="t_Age"> > <xsd:restriction base="t_NonNegativeInt"/> > </xsd:simpleType> > wsdl2ws generates for the first case > typedef xsd__integer t_NonNegativeInt; > which seems absolutely correct to me > but for the second case an empty class t_Age, so the underlying integer is > not accessible. > I would expect > typedef t_NonNegativeInt t_Age; > for the second case. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
