On a related note, I couldn't figure out how to access the ServletContext from 
a request cycle. Anyone knows ?

Henrik
----- Original Message ----- 
From: "Henrik Vendelbo" <[EMAIL PROTECTED]>
To: "Tapestry users" <tapestry-user@jakarta.apache.org>
Sent: Friday, April 15, 2005 7:34 PM
Subject: Re: Service construction, friendly urls


I did, but it doesnt seem to work.

----- Original Message ----- 
From: "Paul Ferraro" <[EMAIL PROTECTED]>
To: "Tapestry users" <tapestry-user@jakarta.apache.org>
Sent: Friday, April 15, 2005 7:18 PM
Subject: Re: Service construction, friendly urls


> That should be configured in your servlet engine, *not* in Tapestry.  If 
> you don't want the servlet context in the url, then you should configure 
> your servlet engine to use a servlet context of "/".
> 
> Paul
> 
> Henrik Vendelbo wrote:
> 
> >I need to do a bit of modification to the friendly urls implementation. I 
> >need to be able to configure wether the servlet context is encoded in the 
> >url. Since it will be applicationwide all instances need the same 
> >configuration. 
> >
> >I think my options are: To access the engine or access the global object. I 
> >suppose that I might not be able to access the global object through 
> >getPage(), so that leaves me with accessing the engine.
> >
> >Any suggestions ?
> >
> >Henrik
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >  
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to