Hi,
I'm testing the RC3 right now and I still have a problem with jaxbri 
databinding:
previous issue (JIRA 3043) is solved (thanks a lot) but now I have another 
problem with the wsdl of another webservice:
     [java] Exception in thread "main" 
org.apache.axis2.wsdl.codegen.CodeGenerationException: 
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
     [java] at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(
CodeGenerationEngine.java:265)
     [java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
     [java] at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
     [java] Caused by: java.lang.RuntimeException: 
java.lang.reflect.InvocationTargetException
     [java] at 
org.apache.axis2.wsdl.codegen.extension.JAXBRIExtension.engage(
JAXBRIExtension.java:112)
     [java] at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(
CodeGenerationEngine.java:218)
     [java] ... 2 more
     [java] Caused by: java.lang.reflect.InvocationTargetException
     [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     [java] at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:64)
     [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:43)
     [java] at java.lang.reflect.Method.invoke(Method.java:615)
     [java] at 
org.apache.axis2.wsdl.codegen.extension.JAXBRIExtension.engage(
JAXBRIExtension.java:101)
     [java] ... 3 more
     [java] Caused by: java.lang.RuntimeException: 
java.lang.RuntimeException: Unable to generate code using jaxbri
     [java] at 
org.apache.axis2.jaxbri.CodeGenerationUtility.processSchemas(
CodeGenerationUtility.java:177)
     [java] ... 8 more
     [java] Caused by: java.lang.RuntimeException: Unable to generate code 
using jaxbri
     [java] at 
org.apache.axis2.jaxbri.CodeGenerationUtility.processSchemas(
CodeGenerationUtility.java:152)
     [java] ... 8 more
     [java] Java Result: 1

I'm using following ant task:
<java classname="org.apache.axis2.wsdl.WSDL2Java" fork="true">
                        <classpath refid="axis.classpath" />
                        <arg value="-d" />
                        <arg value="jaxbri" />
                        <arg value="-uri" />
                        <arg file="${dir.wsdl}/${uri.wsdl}" />
                        <arg value="-ss" />
                        <arg value="-g" />
                        <arg value="-sd" />
                        <arg value="-ssi" />
                        <arg value="-o" />
                        <arg file="output" />
                </java>

The WSDL is correctly parsed and the code generated when using official 
jaxb 2.0.5 distribution and the included xjc.bat script file.

Do I create a JIRA with the faulty wsdl?

Thnaks, 
Pierre





Deepal jayasinghe <[EMAIL PROTECTED]> 
03/08/2007 14:56
Veuillez répondre à
axis-user@ws.apache.org


A
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]>, 
"axis-user@ws.apache.org" <axis-user@ws.apache.org>
cc

Objet
[Axis2] Axis2 1.3 RC3 released






Hi all,

I have uploaded Axis2 1.3 RC3 into my Apache home location [1] . This
release does not have any SNAPSHOT dependencies and we have fixed a
number of issues between RC2 and RC3 so please test the release
candidate as much as you can. My plan is to make this is final RC and
upload the final release on coming Monday 6th Aug 2007 for voting.

You can find the release plugings [2] and the maven2 repo is available
at [3].

When we test please try to cover the following
 - Code generation
 - Sessions
 - Web application
 - In different application servers
- Both JDK 1.5 and JDK 1.4
- Java2WSDL
- POJOs
- And what ever the JIRA we have marked as fixed.


[1] : http://people.apache.org/~deepal/axis2/1.3-RC3/
[2] : http://people.apache.org/~deepal/axis2/1.3-RC3/tools/
[3] : http://people.apache.org/~deepal/axis2/1.3-RC3/m2-repo/

Thanks
Deepal


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to