JBossWS 1.0.X, JAX-WS compliant JBossWS 2.0 and services com

[jova73]

Hi,
I'm starting in these days to develop new web services for an existing J2EE application and I'm considering using JBoss 4.0.5 and the embedded JBossWS 1.0.3 support. Will my web services be compatible with the new JAX-WS compliant web service stack in JBoss 5??

If now I use JAX-WS RI with JBoss 4, will the migration to JBoss 5 and the JAX-WS compliant JBossWS be easier?

Is it possible, in JBossWS 1.0.X and 2.0 (JAX-WS in general), to commit to a WSDL and not to a Java endpoint? That would solve my problem...
What do you think?

Thanks in advance,
Andrea

[dwin]

hey Andrea

you can use the annotation @wsdlLocation to bind your SEI (service end point) to a WSDL. That way the SEI has to confirm to the WSDL.

also, you could always do wsgen (WSDL to java) to generate the SEI and the relevant datatypes.

To answer your question about moving your JBossWS 1.0.3 to JBossWS 1.2.x and JBossWS 2.x, I would imagine it would be a relatively painless transition.

You use your webservice interface (from JAX RPC) as your service interface and tag it with the annotation @Webservice. The JBoss runtime should automatically pick it up.

[jova73]

Hi Dwin,
thank you very much for your response!

Andrea