axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Patrick (JIRA)" <>
Subject [jira] [Commented] (AXIS2-5317) import and element within types->schema failing
Date Wed, 08 Aug 2012 21:03:20 GMT


John Patrick commented on AXIS2-5317:

I don't understanding your comment.

I was asking you to confirm which version that you where using when testing.

I was using 1.6.2 as that is what I raised the ticket against.

> import and element within types->schema failing
> -----------------------------------------------
>                 Key: AXIS2-5317
>                 URL:
>             Project: Axis2
>          Issue Type: Bug
>          Components: codegen, wsdl
>    Affects Versions: 1.6.1, 1.6.2
>         Environment: $ java -version
> java version "1.6.0_31"
> Java(TM) SE Runtime Environment (build 1.6.0_31-b04-415-10M3635)
> Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01-415, mixed mode)
> $ mvn -version
> Apache Maven 3.0.4 (r1232337; 2012-01-17 08:44:56+0000)
> Maven home: /opt/local/share/java/maven3
> Java version: 1.6.0_31, vendor: Apple Inc.
> Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x", version: "10.6.8", arch: "x86_64", family: "mac"
> $ 
>            Reporter: John Patrick
>              Labels: element, generation, import, schema, types, wsdl2java
> I've been given a live wsdl where I'm working and wsdl2java is unable to generate the
java code. I'm using the maven plugin but I also get the same from the command line.
> From my understanding the wsdl is valid, but if you have both import and element within
schema it appears like it doesn't merge the element into the import.
> Files can be found at
> Put the xsd's and wsdl into src/main/resource relative to the pom.xml and the "mvn clean
install" will show the error.
> For a console log of my error, see

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message