Re: Problem with the xsl:import

t use relative paths > as it doesn't "know" what context it resides in (even if Tomcat does). > > Thanks > Geoff > > > -Original Message- > From: Marc Farrow [mailto:[EMAIL PROTECTED] > Sent: 25 April 2006 13:03 > To: Tomcat Users List > S

RE: Problem with the xsl:import

ssage- From: Tim Funk [mailto:[EMAIL PROTECTED] Sent: 25 April 2006 13:17 To: Tomcat Users List Subject: Re: Problem with the xsl:import Here's the problem. xsl:import is purely an XSL thing. So it doesn't necessarily do anything similar to how the servlet spec does things. So wh

RE: Problem with the xsl:import

TECTED] Sent: 25 April 2006 13:03 To: Tomcat Users List Subject: Re: Problem with the xsl:import This has to do with how HTTP requests are processed on your server. You control (by url pattern matching or some other technique) which "service" (Tomcat or Apache) gets to handle the

Re: Problem with the xsl:import

Here's the problem. xsl:import is purely an XSL thing. So it doesn't necessarily do anything similar to how the servlet spec does things. So when you have - cowbell is retreived in a relative style with respect to its context. (which could be file, or http). Your webapp lives in a context. B

Re: Problem with the xsl:import

; I'm not sure quite what you mean by "make sure XSL content is Processed by > Tomcat". I assume this is happening as if we put in the full address the > XSLT is processed with no problem. > > Thanks > Geoff Bland > > > -Original Message- > From:

RE: Problem with the xsl:import

lem. Thanks Geoff Bland -Original Message- From: Marc Farrow [mailto:[EMAIL PROTECTED] Sent: 25 April 2006 12:29 To: Tomcat Users List Subject: Re: Problem with the xsl:import It is not impossible. Try You just have to make sure that the XSL content is either 1) Processed by Tom

Re: Problem with the xsl:import

between servers. > > What we need is a "relative" import, for example, > > > > But I'm thinking this is impossible. > > Thanks > Geoff > > > -----Original Message- > From: Marc Farrow [mailto:[EMAIL PROTECTED] > Sent: 21 April 2

RE: Problem with the xsl:import

grate updated versions between servers. What we need is a "relative" import, for example, But I'm thinking this is impossible. Thanks Geoff -Original Message- From: Marc Farrow [mailto:[EMAIL PROTECTED] Sent: 21 April 2006 14:41 To: Tomcat Users List Subject: Re:

Re: Problem with the xsl:import

o: http://localhost/aaem/xsl/routesummarycontent.xsl"; /> HTH On 4/21/06, BLAND, Geoff, GBM <[EMAIL PROTECTED]> wrote: > > Using Apache Tomcat 5.0.28 I'm having a problem with the xsl:import > command. > > I have several Tomcat running on the same server (the

Problem with the xsl:import

Using Apache Tomcat 5.0.28 I'm having a problem with the xsl:import command. I have several Tomcat running on the same server (they could be different releases of code so can't share resources). An XSLT script is called via a JSP to convert XML to HTML (). This routesummaryheader.