We do not default to port 80. Nohow. In general, we don't launch the server until it is needed for an endpoint, but we respect the server options you specify when we do that.
I don't know a way offhand to ask us to launch sooner. On Wed, Jul 28, 2010 at 8:35 AM, Glen Mazza <[email protected]> wrote: > > > Milisic Aleksandar wrote: >> >> Hi, >> >> I've already once asked a similar question but am still a bit unclear of >> how the >> standalone Jetty configuration actually works. >> > > Just to clarify, you mean *embedded* Jetty, the servlet container behind the > scenes that CXF uses to implement the Endpoint interface, correct? > Standalone to me means you download Jetty and dump a WAR archive holding the > web service in its /webapps folder (or whatever the folder called in > Jetty-speak). > > > Milisic Aleksandar wrote: >> >> 2. Whenever a new service is to be published, we publish it but *without* >> the >> port number since it should automatically be published to the port number >> Jetty >> is listening on. I have tried doing this, but I get a permission >> >> denied on the socket exception since it automatically tries to publish to >> port >> 80. >> > > I think it's just using 80 by default because you haven't specified the > port. I would think Jetty does not listen on a particular port, it listens > on the port that you tell it to listen to when you publish the Endpoint. > > > Milisic Aleksandar wrote: >> >> Has anybody done this, or is there a concrete example somewhere in the >> documentation? >> >> Cheers! >> > > It needs a bit of updating--and high on my list to do so--but my embedded > Jetty example may be of help for you: > http://www.jroller.com/gmazza/entry/writing_junit_test_cases_for#testjt > > Glen > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Problems-understanding-the-standalone-Jetty-configuration-tp2256625p2256675.html > Sent from the cxf-user mailing list archive at Nabble.com. >
