cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <>
Subject Re: wsdl2java tool limitation (package naming for JAXB entities + passing additional arguments to CJX)
Date Thu, 18 Dec 2008 19:07:35 GMT
On Wednesday 17 December 2008 4:09:27 pm Rao, Sameer V wrote:
> CXF 2.1.3. I have two observation regarding the wsdl2java plugin-
> 1. In wsdl2java, for a JAXWS front-end usecase, the -p parameter
> (package name for service interface) also is getting passed to XJC, so
> Service interface and JAXB classes get generated in the same package. Is
> that expected behaviour or is just a byproduct of the fact that both XJC
> and wsdl2Java use -p as a argument for Package? Will it be possible for
> wsdl2java to accept a separate parameter like
> "-bindgingpackage" that can be passed to XJC instead of the passing the
> pacakge name of the service interface.

Personally, I'd like to deprecate/remove the -p option entirely.   It's too 
easy to shoot yourself in the foot with it and produce code that won't work.    
Either that or require it to use the namespace=package flags to specify a 
unique package for each namespace.    In general, I suggest using binding 

> 2. wsdl2java has feature to only pass XJC plugins through the wsdl2java
> but no way to pass "XJC arguments".
> 	e.g. -npa (this is to suppress the generated of
> , -nv.

Theres a bug in JAXB that prevent this from working:

> Is there any chance these could be implemented/supported in future
> release?

Please go vote on that issue.   If the JAXB folks could fix that problem, then 
we could get them to work.

Daniel Kulp

View raw message