<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=US-ASCII" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Hi Chris,<br>
<br>
> 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 <br>
> <a class="moz-txt-link-freetext" href="http://jira.jboss.com/jira/browse/JBWS-1115">http://jira.jboss.com/jira/browse/JBWS-1115</a><br>
<br>
Lets ask Darran about this. He resolved the issue and quotes <br>
<br>
</tt>
<blockquote><tt><i>if no port is specified in the jboss-beans.xml the
ports will be automatically discovered by querying the list of deployed
Tomcat connectors.</i></tt><br>
<br>
<tt><i>one-test:</i></tt><br>
<tt><i> [junit] Running
org.jboss.test.ws.jaxrpc.jbws1115.JBWS1115TestCase</i></tt><br>
<tt><i> [junit] Tests run: 2, Failures: 0, Errors: 0, Time
elapsed: 0.266 sec</i></tt><br>
</blockquote>
<tt>Let me also look into the test case and make sure it does what it
is supposed to do.<br>
<br>
> 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). <br>
> It seems like it is currently the case with 1.0.4. Is this correct?<br>
<br>
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.<br>
<br>
> can someone look at <a class="moz-txt-link-freetext" href="http://jira.jboss.com/jira/browse/JBWS-1515">http://jira.jboss.com/jira/browse/JBWS-1515</a><br>
<br>
I commented.<br>
<br>
> <a class="moz-txt-link-freetext" href="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQClientUsingProxy">http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQClientUsingProxy</a>
provides an outdated link<br>
<br>
done. thanks<br>
<br>
cheers<br>
-thomas<br>
</tt><br>
Chris Laprun wrote:
<blockquote cite="midEC9DF828-D162-4BDA-8849-8D64356E8C1D@redhat.com"
type="cite">Hi Thomas,
<br>
<br>
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
<a class="moz-txt-link-freetext" href="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQURLRewriting">http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQURLRewriting</a>. 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 <a class="moz-txt-link-freetext" href="http://jira.jboss.com/jira/browse/JBWS-1115">http://jira.jboss.com/jira/browse/JBWS-1115</a>. 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.
<br>
<br>
Could you detail the process on how to JBoss WS deals with ports? More
precisely, I'm interested in the following use cases:
<br>
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?
<br>
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)?
<br>
<br>
Also, unrelated but of importance: can someone look at
<a class="moz-txt-link-freetext" href="http://jira.jboss.com/jira/browse/JBWS-1515">http://jira.jboss.com/jira/browse/JBWS-1515</a>? This is blocking for us.
<br>
Finally,
<a class="moz-txt-link-freetext" href="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQClientUsingProxy">http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQClientUsingProxy</a>
provides an outdated link...
<br>
<br>
Best,
<br>
Chris
<br>
<br>
==
<br>
JBoss Portal Developer / WSRP Lead
<br>
JBoss, a division of Red Hat
<br>
<br>
<br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
</pre>
</body>
</html>