Yes, in general the artifacts generated by the wsdl-2-java process are
generic and will work on whatever WS runtime (Metro/JAX-WS RI or CXF
typically) you have loaded. Certain Metro and CXF extensions might
bring in CXF- or Metro-specific imports into the generated files,
however, breaking portability.
JaxWSProxyFactoryBean
(http://cxf.apache.org/javadoc/latest/org/apache/cxf/jaxws/JaxWsProxyFactoryBean.html)
is CXF-specific so if you're using it you'll have the CXF libraries
loaded. I doubt the CXF Spring config can work on another web service
stack, but it's best anyway to first choose the web service stack you
wish to use, and then use that library's Spring configuration options to
configure it (Metro has its own: http://metro.java.net/guide/, search on
"Spring").
Glen
On 02/21/2012 06:37 AM, [email protected] wrote:
Hi all,
I generated a client with maven cxf-codegen-plugin. The generated classes -
correct me if Im worng - let the application server(e.g. WAS) choose the WS
runtime.
For better integration in spring I tried to generate the client with
JaxWsProxyFactorybean. Is It possible, that this way lead to the problem, that
always the cxf runtime is used? Can I use JaxWsProxyFactoryBean and let the
application server provide the runtime?
Thx
mephi :)
--
Glen Mazza
Talend Community Coders - coders.talend.com
blog: www.jroller.com/gmazza
