2 Replies Latest reply on May 27, 2005 1:13 PM by Bruce

    Context problem upgrading from AXIS on JBoss 3.2

    Bruce Newbie


      I'm in the process of upgrading a existing set of web services from AXIS on JBoss 3.2 to JBoss 4. On the old setup, web services in 2 EJB modules and 1 web module were all exposed as /services/serviceName.

      Initially I just tried to keep the AXIS setup, but found that on JBoss 4.0.1 AXIS couldn't find the class to deploy services for the SS beans. I changed the SS beans to use JBossWS, and left the web module using AXIS (because it contains a ton of AXIS-generated code supporting complex data types). All web services now work, but I can't get them to share the /services/ context (which is important because there are several hundred deployed client applications). If I configure them all to use /services/ as a context, then 2 of the 3 applications aren't accessible via the /services/serviceName URL.

      I've now moved to JBoss 4.0.2, but have the same problem. How can I configure 4.0.2 to give me the same service URL's as we had with JBoss 3.2 and AXIS?