Hi Chris, > WS is supposed to be able to pick up the port number on which the server is running if no port is specified in jboss-beans.xml according to > http://jira.jboss.com/jira/browse/JBWS-1115 Lets ask Darran about this. He resolved the issue and quotes

if no port is specified in the jboss-beans.xml the ports will be automatically discovered by querying the list of deployed Tomcat connectors.

one-test:
[junit] Running org.jboss.test.ws.jaxrpc.jbws1115.JBWS1115TestCase
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.266 sec

Let me also look into the test case and make sure it does what it is supposed to do. > Ideally, no changes would be required in our web service configuration (i.e. we don't want our users to have to change several configuration files). > It seems like it is currently the case with 1.0.4. Is this correct? Yes that is correct. Unless JBWS-1115 is truly resolved (which you claim it is not) the user will have to modify the jbossws configuration. > can someone look at http://jira.jboss.com/jira/browse/JBWS-1515 I commented. > http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQClientUsingProxy provides an outdated link done. thanks cheers -thomas
Chris Laprun wrote:

Hi Thomas,

I am quite confused as to how JBoss WS handles changes to the port on which JBoss AS runs. We have consumers running Portal on non-standard ports or wanting to use WSRP over HTTP+SSL. I have looked at the documentation and http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQURLRewriting. As of 1.0.4.GA, WS is supposed to be able to pick up the port number on which the server is running if no port is specified in jboss-beans.xml according to http://jira.jboss.com/jira/browse/JBWS-1115. However, if it doesn't seem to work for https. According to the documentation, you need to manually override the soap-address for WS to pick up the correct port. This is extremely inconvenient from a user perspective so I am thinking I might be missing something.

Could you detail the process on how to JBoss WS deals with ports? More precisely, I'm interested in the following use cases:
1. A user changes the default port for JBoss Web. Ideally, no changes would be required in our web service configuration (i.e. we don't want our users to have to change several configuration files). It seems like it is currently the case with 1.0.4. Is this correct?
2. A user wants to access our web service over SSL. Is it possible to configure the web service in such a way that users can access both the secure and unsecure version without having to tweak the configuration (that is once they've specified the appropriate connectors for JBoss Web)?

Also, unrelated but of importance: can someone look at http://jira.jboss.com/jira/browse/JBWS-1515? This is blocking for us.
Finally, http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQClientUsingProxy provides an outdated link...

Best,
Chris

==
JBoss Portal Developer / WSRP Lead
JBoss, a division of Red Hat

-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx