You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Jean-Sebastien Delfino <js...@apache.org> on 2007/07/31 18:55:20 UTC
Embedded servers now correctly support multiple ports, was: Binding
endpoints (was Fwd: Services and WSDL files
[snip]
Jean-Sebastien Delfino wrote:
>
>>
>> All those sound good, and just to add one more, i think there's a bug
>> (unless its been fixed recently) in the standalone jetty/tomcat
>> runtimes so
>> that the port in a endpoint url is used but only for the first
>> endpoint. So
>> if you have two binding uri's http://localhost:8080/foo and
>> http://localhost:8085/bar then both services are exposed on the same one
>> port and its just whichever port happened to get processed first.
>
> Yes, I've bumped into this one several times too... so I'd like to
> volunteer to fix it.
>
>
This is now fixed, you should be able to register servlets under
different port numbers and both the JettyServer and TomcatServer will
take care of starting embedded servers listening on these ports.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Embedded servers now correctly support multiple ports, was: Binding
endpoints (was Fwd: Services and WSDL files
Posted by Simon Nash <na...@hursley.ibm.com>.
Sorry, I did not see this before doing the checkout and testing that
led to my creating TUSCANY-1501. I have rerun my test against the
latest trunk code and this is working now. I'll close TUSCANY-1501.
Simon
Jean-Sebastien Delfino wrote:
> [snip]
> Jean-Sebastien Delfino wrote:
>
>>
>>>
>>> All those sound good, and just to add one more, i think there's a bug
>>> (unless its been fixed recently) in the standalone jetty/tomcat
>>> runtimes so
>>> that the port in a endpoint url is used but only for the first
>>> endpoint. So
>>> if you have two binding uri's http://localhost:8080/foo and
>>> http://localhost:8085/bar then both services are exposed on the same one
>>> port and its just whichever port happened to get processed first.
>>
>>
>> Yes, I've bumped into this one several times too... so I'd like to
>> volunteer to fix it.
>>
>>
>
> This is now fixed, you should be able to register servlets under
> different port numbers and both the JettyServer and TomcatServer will
> take care of starting embedded servers listening on these ports.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org