Re: [Jetty launcher] How to get it to also listen on an secure port (UNsolved)

["F. Da Costa" <da...@xs4all.nl>]

Geoff Longman wrote:

> Sure, send it along!
> 
.... Just found out that there is something funny going on with the 
retrieval of the images which are located in the context dir (as well as in 
the WEB-INF dir for double check). They are not (retrieved that is).
If only things would cooperate for a change :-(.

I'll get you a modded version as soon as i'v got this fixed.
Don't hesitate if y'v got a suggestion ;-)

Fermin

> Geoff
> ----- Original Message -----
> From: "F. Da Costa" <da...@xs4all.nl>
> To: <ta...@jakarta.apache.org>
> Sent: Thursday, March 11, 2004 9:49 AM
> Subject: Re: [Jetty launcher] How to get it to also listen on an secure port
> (solved)
> 
> 
> 
>>I just noticed (& registered) the entries from the output.
>>
>>Reluctantly i have to say that sticking two /'s in instead of making life
>>difficult with all kinds of tricks did the trick.
>>
>>I'm just going to test a bit further to make sure the whole structure is
>>indeed in ssl mode. When done it basically would fir perfectly in a
> 
> default
> 
>>Spindle project. Send you a copy of the used jetty.xml in that case?
>>
>>Thx again Geoff,
>>
>>Cheers,
>>Fermin
>>
>>
>>Geoff Longman wrote:
>>
>>
>>>----- Original Message -----
>>>From: "F. Da Costa" <da...@xs4all.nl>
>>>To: <ta...@jakarta.apache.org>
>>>Sent: Thursday, March 11, 2004 9:12 AM
>>>Subject: Re: [Jetty launcher] How to get it to also listen on an secure
> 
> port
> 
>>>
>>>
>>>>Hi Geoff,
>>>>
>>>>Just a quick one.
>>>>
>>>>Geoff Longman wrote:
>>>>
>>>>
>>>>>Y'now, I never have written a single line of jetty xml. I never needed
>>>
>>>to.
>>>
>>>
>>>>>Here's the default launch code:
>>>>>
>>>>>Server server = new Server();
>>>>>Log log = Log.instance();
>>>>>OutputStreamLogSink sink = new OutputStreamLogSink();
>>>>>sink.start();
>>>>>log.add(sink);
>>>>>SocketListener listener = new SocketListener();
>>>>>listener.setPort(port);
>>>>>listener.setMaxThreads(10);
>>>>>listener.setMaxIdleTimeMs(30000);
>>>>>listener.setLowResourcePersistTimeMs(2000);
>>>>>listener.setConfidentialPort(8443); // this was a contributed patch -
>>>>>mystery code to me.
>>>>>server.addListener(listener);
>>>>>server.addWebApplication(wContext, contextArg);
>>>>
>>>>What would the values be for wContext and contextArg if it was used in
> 
> the
> 
>>>>following env:
>>>>- jetty home dir: c:\jetty
>>>>- base of project at c:\eclipse3\workspace\testprj
>>>>- the context is (still) called context and at: ${project}\context
>>>>- WEB-INF lives at: ${context}\WEB-INF
>>>
>>>
>>>>From the jetty javadoc:
>>>
>>>wContext- The context path spec. Which must be of the form / or /path/*
>>>contextArg- The Web application directory or WAR file.
>>>
>>>As passed from the launch config,
>>>
>>>wContext is whatever you entered into the "Web context root name" field.
> 
> I
> 
>>>usually leave this blank which means "/" will be used.
>>>
>>>contextArg in your case would be: c:\eclipse3\workspace\testprj\context
>>>
>>>You can see what's passed by looking at the Arguments tab.
>>>
>>>In my case (or a project I'm working on...)
>>>
>>>-context X:\eclipse\e21\worspace\orca-client-tap30\context
>>>-port 8080
>>>-wContext
>>>
>>>The entry for -wContext looks funny because I didn't fill in the field
> 
> on
> 
>>>the first tab. In this case,  the launcher uses "/"
>>>
>>>
>>>
>>>
>>>>I think i've got some stupid warp in my brain that is not getting around
>>>
>>>to
>>>
>>>
>>>>grasping this properly. Prob i'm missing something here because i can
>>>
>>>start
>>>
>>>
>>>>the server incl. 443 port but i can't access the app (which is boring to
>>>>say the least).
>>>>
>>>>TIA
>>>>
>>>>Fermin
>>>>
>>>>
>>>>
>>>>>server.start();
>>>>>
>>>>>and the "launch with Jetty xml file" version:
>>>>>
>>>>>Server server = new Server(file.toURL());
>>>>>server.start();
>>>>>
>>>>>So perhaps the default launch is "not quite good enough". While it does
>>>
>>>set
>>>
>>>
>>>>>this confidential port thingy, it doesn't do all the
>>>>>
>>>>>
>>>>>
>>>
>>><!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
>>>
>>>>>><!-- Add a HTTPS SSL listener on port
>>>
>>>     -->
>>>
>>><!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
>>>
>>>>>><!-- UNCOMMENT TO ACTIVATE
>>>>>
>>>>>
>>>>>stuff. Although I don't understand why just using the xml based lauch
>>>>>wouldnt' work.
>>>>>
>>>>>Hmm, a possible enhancement could be to add another listener in the
>>>
>>>default
>>>
>>>
>>>>>launch iff the "Include SSL support" checkbox is checked on the
>>>
>>>JSP/Extras
>>>
>>>
>>>>>tab..
>>>>>
>>>>>Care to give it a try? It would be weeks before I could get to this.
>>>>>Strike That. Actually, I think this would mean splitting out the
>>>
>>>JSP/Extra
>>>
>>>
>>>>>tab into two tabs,
>>>>>JSP/JMX and SSL, where SSL would need a bunch of fields to specify the
>>>>>parameters needed for the secure listener setup (keystore, passwords,
>>>
>>>etc).
>>>
>>>
>>>>>Not a quick fix for sure.
>>>>>
>>>>>Geoff
>>>>>
>>>>>
>>>>>
>>>>>----- Original Message -----
>>>>>From: "F. Da Costa" <da...@xs4all.nl>
>>>>>To: <ta...@jakarta.apache.org>
>>>>>Sent: Wednesday, March 10, 2004 1:26 PM
>>>>>Subject: Re: [Jetty launcher] How to get it to also listen on an secure
>>>
>>>port
>>>
>>>
>>>>>
>>>>>>Geoff Longman wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>I've never tried this for https, but you can change the port in the
>>>>>
>>>>>launch
>>>>>
>>>>>
>>>>>
>>>>>>>configuration page.
>>>>>>
>>>>>>I can manage the port change ;-). It would however be nice if Jetty
> 
> were
> 
>>>>>to
>>>>>
>>>>>
>>>>>
>>>>>>pick up the https protocol as well, switching from 8080 to 8443 (or so
>>>
>>>it
>>>
>>>
>>>>>>should be according to the jetty.xml file).
>>>>>>
>>>>>>Maybe i should ask a different question instead.
>>>>>>As you know this is part of a jetty.xml file.
>>>>>>
>>>>>> <Set name="rootWebApp">root</Set>
>>>>>> <Call name="addWebApplications">
>>>>>>   <Arg></Arg>
>>>>>>   <Arg><SystemProperty name="jetty.home"
> 
> default="."/>/context/</Arg>
> 
>>>>>>   <!--Arg>org/mortbay/jetty/servlet/webdefault.xml</Arg-->
>>>>>>   <Arg>/web.xml</Arg>
>>>>>>   <Arg type="boolean">true</Arg>
>>>>>> </Call>
>>>>>>
>>>>>>Using the default Spindle created structure how would this part be
>>>
>>>filled
>>>
>>>
>>>>>>in? Because when i run it i get:
>>>>>>java.lang.IllegalArgumentException: No such webapps resource
>>>>>>file:/C:/Jetty/context
>>>>>>
>>>>>>I will persue (stubbornly) but if y've got a tip or two, be my guest
> 
> ;-)
> 
>>>>>>Fermin
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Geoff
>>>>>>>----- Original Message -----
>>>>>>>From: "F. Da Costa" <da...@xs4all.nl>
>>>>>>>To: <ta...@jakarta.apache.org>
>>>>>>>Sent: Wednesday, March 10, 2004 12:35 PM
>>>>>>>Subject: [Jetty launcher] How to get it to also listen on an secure
>>>
>>>port
>>>
>>>
>>>>>>>
>>>>>>>
>>>>>>>>Hi (Geoff?),
>>>>>>>>
>>>>>>>>Just a small question.
>>>>>>>>How do i get Jetty, started via the launcher, to also listen on the
>>>>>
>>>>>secure
>>>>>
>>>>>
>>>>>
>>>>>>>>443 or 8443 port(s)?
>>>>>>>>
>>>>>>>>I've got a https://... link rendered and what i gathered from the
> 
> doc
> 
>>>i
>>>
>>>
>>>>>>>>could find it should be handled no worries. But i guess Jetty needs
> 
> to
> 
>>>>>be
>>>>>
>>>>>
>>>>>
>>>>>>>>listening on the port.
>>>>>>>>
>>>>>>>>How do i go about that (or do i have to whip up an external
> 
> jetty.xml.
> 
>>>>>>>>TIA
>>>>>>>>Fermin DCG
>>>>>>>>
>>>>>>>>
>>
>>>>>>>---------------------------------------------------------------------
>>>>>>>
>>>>>>>>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>>>>>>>For additional commands, e-mail:
> 
> tapestry-user-help@jakarta.apache.org
> 
>>>>>>>
>>>>>>>
>>>>>>>---------------------------------------------------------------------
>>>>>>>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>>>>>>For additional commands, e-mail:
> 
> tapestry-user-help@jakarta.apache.org
> 
>>>>>>>
>>>>>>
>>>>>>---------------------------------------------------------------------
>>>>>>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>>>>>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>---------------------------------------------------------------------
>>>>>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>>>>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>>---------------------------------------------------------------------
>>>>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>>>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>>>
>>>
>>>
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>>
>>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org