Hi Howard,

I just tried this myself and can confirm that there's a bug in the JiBX 
1.2.2 Jibx2Wsdl code. Sorry - the normal build steps don't invoke the 
Axis2 code, so I hadn't noticed this.

I'll get the problem fixed and update JiBX with a 1.2.3 release this week.

Thanks,

  - Dennis

Dennis M. Sosnoski
XML and Web Services in Java
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117



Houwu Bai wrote:
> Hi all,
>
> I tried to build jibx2wsdl examples. But for all five examples in the 
> directory examples/jibx2wsdl I got the same error message:
>
> how...@howard:~/Downloads/jibx-1.2.2/examples/jibx2wsdl/example4$ ant clean 
> generate-wsdl generate-server
> Buildfile: build.xml
>
> clean:
>
> compile-starter:
>     [mkdir] Created dir: 
> /home/howard/Downloads/jibx-1.2.2/examples/jibx2wsdl/example4/start/bin
>      [echo] Compiling starting classes
>     [javac] Compiling 11 source files to 
> /home/howard/Downloads/jibx-1.2.2/examples/jibx2wsdl/example4/start/bin
>
> generate-wsdl:
>     [mkdir] Created dir: 
> /home/howard/Downloads/jibx-1.2.2/examples/jibx2wsdl/example4/gen
>      [echo] Running Jibx2Wsdl tool
>
> generate-server:
>      [echo] Running WSDL2Java task
>     [mkdir] Created dir: 
> /home/howard/Downloads/jibx-1.2.2/examples/jibx2wsdl/example4/server/gen
>      [java] Retrieving document at 
> '/home/howard/Downloads/jibx-1.2.2/examples/jibx2wsdl/example4/gen/LibraryServer2.wsdl'.
>      [java] Exception in thread "main" 
> org.apache.axis2.wsdl.codegen.CodeGenerationException: 
> java.lang.RuntimeException: No element reference in message 
> addItemResponseMessage
>      [java]     at 
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:271)
>      [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: No element reference in 
> message addItemResponseMessage
>      [java]     at 
> org.apache.axis2.jibx.CodeGenerationUtility.unwrapMessage(CodeGenerationUtility.java:697)
>      [java]     at 
> org.apache.axis2.jibx.CodeGenerationUtility.engage(CodeGenerationUtility.java:394)
>      [java]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>      [java]     at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>      [java]     at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>      [java]     at java.lang.reflect.Method.invoke(Method.java:597)
>      [java]     at 
> org.apache.axis2.wsdl.codegen.extension.JiBXExtension.engage(JiBXExtension.java:77)
>      [java]     at 
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224)
>      [java]     ... 2 more
>
> BUILD FAILED
>
> The version of Jibx is 1.2.2. For Axis2, I tried both version 1.5.1 and 1.4.1.
>
>
> Regards,
> Howard
>
>
>
>       
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> jibx-users mailing list
> jibx-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jibx-users
>
>   

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
jibx-users mailing list
jibx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-users

Reply via email to