See inline.
Simon
ant elder wrote:
On 9/7/07, Luciano Resende [EMAIL PROTECTED] wrote:
On 9/7/07, Simon Nash [EMAIL PROTECTED] wrote:
I'm a bit concerned with this default as it would cause conflicts
if I have a Web app server active on port 8080 while I'm running a
test that uses
On 9/7/07, ant elder [EMAIL PROTECTED] wrote:
Right now that would be down to the ServletHost impl that you use,
currently
our Jetty and Tomcat ServletHost impls both have port 8080 as the default.
...ant
On 9/7/07, Simon Nash [EMAIL PROTECTED] wrote:
What is the default for the
On 9/7/07, Simon Nash [EMAIL PROTECTED] wrote:
I'm a bit concerned with this default as it would cause conflicts
if I have a Web app server active on port 8080 while I'm running a
test that uses either of these environments.
Yes, using 8080 would conflict with existing web app servers running
I'm a bit concerned with this default as it would cause conflicts
if I have a Web app server active on port 8080 while I'm running a
test that uses either of these environments.
Is there any problem with changing this default setting for our
embedded ServletHost from 8080 to 8085? This should
Right now that would be down to the ServletHost impl that you use, currently
our Jetty and Tomcat ServletHost impls both have port 8080 as the default.
...ant
On 9/7/07, Simon Nash [EMAIL PROTECTED] wrote:
What is the default for the environment? For a webapp deployment
this seems
On 9/7/07, ant elder [EMAIL PROTECTED] wrote:
I'd like to remove the hard coded BASE_URI constant from the Axis2 WS
binding Axis2ServiceProvider so that the default for the environment is
used
instead of always using port 8085 unless its explicitly stated in the
binding uri. Can anyone see
What is the default for the environment? For a webapp deployment
this seems meaningful, but I'm not sure what this would be for
host-embedded with http-jetty or http-tomcat.
Simon
ant elder wrote:
I'd like to remove the hard coded BASE_URI constant from the Axis2 WS
binding
I'd like to remove the hard coded BASE_URI constant from the Axis2 WS
binding Axis2ServiceProvider so that the default for the environment is used
instead of always using port 8085 unless its explicitly stated in the
binding uri. Can anyone see any problems with doing this? A quick try shows
On 9/7/07, Luciano Resende [EMAIL PROTECTED] wrote:
On 9/7/07, Simon Nash [EMAIL PROTECTED] wrote:
I'm a bit concerned with this default as it would cause conflicts
if I have a Web app server active on port 8080 while I'm running a
test that uses either of these environments.
Yes,
