Yep, it will work. Also, if felix.httpservice implementation uses Jetty6 right ? If so, it already works when setting the port to 0. Anyhow, this port will not really be propagated, so i am unsure how an automated test should rely on it. Sure, the "server" will start on port X. But X is not known for any polling clients. Not sure if its of question at all.
On 7/7/09, Angelo van der Sijpt (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/ACE-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727948#action_12727948 > ] > > Angelo van der Sijpt commented on ACE-33: > ----------------------------------------- > > I noticed that Pax Web 0.6.0 can find a port itself; might that help us in > this case? > see http://wiki.ops4j.org/display/paxweb/Pax+Web+-+0.6.0 , > http://issues.ops4j.org/jira/browse/PAXWEB-126 > >> Make used ports easily configurable so we can run on the build server >> using different ports >> ------------------------------------------------------------------------------------------- >> >> Key: ACE-33 >> URL: https://issues.apache.org/jira/browse/ACE-33 >> Project: Ace >> Issue Type: Improvement >> Reporter: Marcel Offermans >> >> Currently, the build on the automatic build server is failing because some >> tests need a running framework with a webserver running on port 8080. For >> some reason the current build agent does not have that port available. We >> should be able to easily reconfigure the ports we use in our applications >> to deal with these situations. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > > -- Toni Menzel Independent Software Developer Professional Profile: http://okidokiteam.com [email protected] http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software.
