so I installed Axis-1_2RC2 on my box.
That JBossWS uses Axis internally is an implementation detail that is going to be removed. If you want to do J2EE compliant portable WS, you do not need to install any other Axis version then the one we provide.
Of course use whatever SOAP stack you prefer on the client.
You can use the ant java task with wscompile.
Ok, but any opinion on whether I should use JWSDP or use Axis? I'm trying to identify those jars as well as figure out how to generate the WSDL from my SEI. The Wiki docs dont' say much on this aspect of it. Are there any JBoss examples on generatiing WSDL files?
AFAIK all wiki examples use wscompile. Axis's Java2WSDL does not generate the required WS4EE deployment artifacts like jaxrpc-mapping.xml.
Which wiki is not clear enough?
I saw there is an Axis C++ package from Apache. Could Axis C++ be used to build C++ webservices that work inconjuction with JBoss? Does JBoss have a similar, already integrated package? would you recommend using Axis-C++ for this purpose? Do you know of any articles that discuss how to install, integrate and use this combination?
You should look for a SOAP stack that is BasicProfile-1.0 compliant. Is that the case with the new Axis C++?