| Key: |
AXIS2-660
|
| Type: |
New Feature
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Minor
|
| Assignee: |
Unassigned
|
| Reporter: |
Kenneth Tam
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
05/May/06 11:37 AM
|
|
I've added support for using the JAX-B RI with WSDL2Java. This patch just includes the initial support to get the appropriate databinding extension registered, and calling the RI's XJC compiler. Code gen is working for basic cases -- I have not yet started on runtime support.
I've followed the reflection-based pattern for loading the RI, per the recent changes in the XMLBeans and JiBX binding extensions. Compile-time deps on the RI are limited to the new jaxbri module, and at runtime if the JAX-B RI JARs are not available on the classpath, WSDL2Java will throw an appropriate exception & msg.
A sample command line:
wsdl2java -uri foo.wsdl -d jaxbri
|
|
Description
|
I've added support for using the JAX-B RI with WSDL2Java. This patch just includes the initial support to get the appropriate databinding extension registered, and calling the RI's XJC compiler. Code gen is working for basic cases -- I have not yet started on runtime support.
I've followed the reflection-based pattern for loading the RI, per the recent changes in the XMLBeans and JiBX binding extensions. Compile-time deps on the RI are limited to the new jaxbri module, and at runtime if the JAX-B RI JARs are not available on the classpath, WSDL2Java will throw an appropriate exception & msg.
A sample command line:
wsdl2java -uri foo.wsdl -d jaxbri
|
Show » |
|
Support JAX-B RI databinding for WSDL2Java
