It'd be better to port your WS endpoints to J2EE-1.4 compliant endpoints.
i'm newbie on JBoss and Web Services
Is there another solution for porting the application on JBoss 4 without modify it ????
I realize that J2EE-1.4 web services (WS4EE) has a steep learning curve, which is greatly simplified by JSR181 endpoints.
I would recommend you invest a little in learnig about the standard way of doing WS. Its in the nature of standards that they protect the such investment.
Reading the user guide and studying the samples that come with the user guide should get you there.
I want to know JBossWS is a standalone module which can be plugged into any other application server or just stick to JBoss AS?
Another question is if I use JBossWS wstool to generate artifects and stub/dynamic proxy/DII stuff, can these JBossWS generated files work under AXIS implementation or JWSDP implementation?
If you _need_ to use Axis 1.1 as I did, I think just removing the jbossws.sar (from JBoss AS 4.0.4CR2) worked for me. I deploy the Axis 1.1 jars with my ear and it seems to be working fine - but I do plan on migrating to the new JBossWS as soon as I can get my app ported.
Thanks for the reply. We build our webservice application based on JWSDP 1.6 (use JWSDP artifects) and deploy it under JBossWSEE (AXIS implementation)on 4.0.3SP1, it works to me by calling WSDL with JWSDP stub and Dynamic proxy(casting to use JBossFactoryImpl and explictely call JBoss createService() and point to the jaxprc mapping), but fail in DII. Even deployed that jar file in 4.0.4RC2(JBossWS), it also work to me but not DII. We use document/literal by the way.
So I wonder is it possible deployed AXIS/JWSDP/JBOSSWS within JBossWS
and let all the client tier use the standard JAXRPC API (generic stub and change the WSDL on the fly or hook up JUDDI).
Our purpose is to have a generic solution in both server and client side. All the implemenation is vendor transparent stick to the standard spec. Do you think it possible? If possible, how to implement it?
One more thing, all our implementation don't involve vernder specific code , only stick to the JSR-109 POJO Endpoint/JSR-109 Clients.
If you use the JSR-109 endpoint/client deployment model, you are by definition portable.