WS URL different for 4.2.2 and 4.2.3

[karypid]

Hello,

I have two installations of JBoss on my machine (4.2.2 and 4.2.3). In both of them, I have installed JBossWS-Native 3.0.2. When I deploy an EAR that has a EJB-JAR with a web service, I observed that my WS is published in different URL location:

https://localhost:8080/ear_name-ejbjar_name/MyServiceBean?wsdl
https://localhost:8180//MyServiceBean?wsdl

The different port (8080 and 8180) is because I have changed the ports for the 4.2.3 installation so that I may run both of them concurrently. However, 4.2.2 uses the ear/ejb-jar names as a prefix whereas 4.2.3 does not.

The stange thing is that BOTH use the latest stable JBossWS-native stack (i.e. 3.0.2) so I guess the publish location is not controlled fully by JBossWS.

How can I get 4.2.3 to revert back to the old behaviour? Does this seem like a bug in the Application Server?

[karypid]

I've been toying with this for a while. I was able to use jboss.xml to provide a proper URL-prefix for 4.2.3 using jboss.xml:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE jboss PUBLIC
 "-//JBoss//DTD JBOSS 4.2//EN"
 "http://www.jboss.org/j2ee/dtd/jboss_4_2.dtd">
<jboss>
 <security-domain>java:/jaas/JBossWS</security-domain>
 <webservices>
 <context-root>TYPE_YOUR_PREFERRED_URL_HERE</context-root>
 </webservices>
</jboss>

Unfortunately, 4.2.2 seems to completely ignore this!

Anyway, I like the 4.2.3 behavior better (being able to specify the URL prefix of your choice).

[asoldano]

That's most probably because of this: https://jira.jboss.org/jira/browse/JBWS-1813
IOW there was a bug which was fixed in AS 4.2.3.GA.