axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim West (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AXIS2-3994) WSDL2Java with ADB binding bug on WSDL with two mutually-importing schemas
Date Wed, 03 Sep 2008 01:03:44 GMT

     [ https://issues.apache.org/jira/browse/AXIS2-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tim West updated AXIS2-3994:
----------------------------

    Attachment: AXIS2-3994-demonstration.zip

The two WSDLs (and associated build.xml files for invocation of WSDL2Java) demonstrate this
problem. The schemas are identical, except that in one they are embedded within the wsdl (under
the <wsdl:types> element) and in the other they are imported via wsdl:import.

The version that imports the schemas works - WSDL2Java is able to generate an ADB binding
for the schema. The version that has embedded schemas does not work - an error "WARN   org.apache.axis2.schema.SchemaCompiler
Type {http://schema1.company.com/}EmbeddedElement missing!" is emitted during generation.

> WSDL2Java with ADB binding bug on WSDL with two mutually-importing schemas
> --------------------------------------------------------------------------
>
>                 Key: AXIS2-3994
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3994
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: adb, codegen, Tools
>    Affects Versions: 1.4.1
>         Environment: Windows XP SP2, Java 1.5.0_06
>            Reporter: Tim West
>         Attachments: AXIS2-3994-demonstration.zip
>
>
> WSDL2Java fails to correctly generate an ADB stub for this WSDL: https://www.foxtel.com.au/EPGServiceWrapper/WebService/EPG/EPGServiceWrapper.wsdl.
> The following is printed during generation:
>   [codegen] 2008.08.28 15:13:01.640 WARN   org.apache.axis2.schema.SchemaCompiler Type
{http://rbsw.foxtel.com.au/}BookingRequest missing!
> This means that in the generated code, BookingRequest objects are represented as OMElements
rather than as objects based on the schema.
> My initial notes from investigation:
>  * The WSDL contains two embedded schemas, both of which import each other (via an xsd:import).
I suspect this is part of the problem.
>  * I *think* the WSDL is valid - that is, (1) Axis 1 version 1.4 can handle the WSDL
fine, and the generated code actually works, and (2) Axis2 1.4 with the XMLBeans binding runs
without errors (though I did not test this client).
> I am invoking WSDL2Java as follows:
> 		<codegen wsdlfilename="${wsdl.uri}" 
> 			synconly="true" 
> 			serverside="false"
> 			allports="true" 
> 			language="java"
> 			skipwsdl="false"
> 			packagename="com.foxtel.rbs.client.binding" 
> 			databindingname="adb"
> 			output="${build.dir}/client" 
> 			generateservicexml="false"
> 			servicename="RemoteBookingServiceWrapper">
> 		</codegen>
> I have searched through Jira and cannot find a similar issue to this one - sorry if I've
missed anything.

-- 
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message