You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Eric Pugh <ep...@upstate.com> on 2006/01/03 04:05:39 UTC
Re: turbine 2.3.2 - XSLT uri problem
Raoul,
I know you sent me something, but I think I lost it, or couldn't get
it working. I'll echo Siegfried and ask you to make sure it doesn't
require TurbineServlet and we would happily apply it!
ERic
On Dec 30, 2005, at 2:40 PM, Siegfried Goeschl wrote:
> Hi Raoul,
>
> +) it seems that the patch was applied TURBINE_2_3_BRANCH and not
> the trunk - we should apply the path to the trunk
> +) the patch can't be applied directly to Fulcrum since there is no
> TurbineServlet and running in a servlet container is not mandatory
> for Fulcrum /not even Turbine btw)
>
> Cheers,
>
> Siegfried Goeschl
>
> rc wrote:
>
>> Hi all,
>>
>> Thanks for help, but I would have prefered using turbine built-in
>> services (easily upgradable)
>>
>> I think it's a bug that has to be corrected (when some of us have
>> enough time), the more so as
>> the new XSLtransformer class is more powerful (xsl parameters, ...).
>>
>> Any suggestions ?
>>
>> Bye
>>
>> Raoul
>>
>> Siegfried Goeschl wrote:
>>
>>> Hi Raoul,
>>>
>>> I implemented a cousin of XSLT service based on DOM4J - would
>>> this be an option for you?
>>>
>>> Cheers,
>>>
>>> Siegfried Goeschl
>>>
>>> rc wrote:
>>>
>>>> Thomas Vandahl wrote:
>>>>
>>>>> Hi Raoul,
>>>>>
>>>>> this was a change of mine. The XSLT service of Turbine now uses
>>>>> URLs and the ServletContext methods to access the .xsl-files.
>>>>> This is a step to get Turbine to run from a .war-file.
>>>>>
>>>>> In your case I'd suggest to change the include path to an
>>>>> absolute URL such as "http://somehost/xsl/tools.xsl" This
>>>>> should fix the problem.
>>>>>
>>>>> Bye, Thomas.
>>>>>
>>>>
>>>> Hi,
>>>> I understand your objectives, but I can't use absolute constant
>>>> url in my xsl include@href path. I can
>>>> only use relatives or dynamic(servlet context) uris. But as you
>>>> know, we can't use dynamic data inside include@href values.
>>>>
>>>> So, I'm always blocked on this point.
>>>> By
>>>>
>>>> Raoul
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
>>>> For additional commands, e-mail: turbine-user-
>>>> help@jakarta.apache.org
>>>>
>>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail: turbine-user-
>>> help@jakarta.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: turbine 2.3.2 - XSLT uri problem
Posted by rc <rc...@datasystem.fr>.
Hi,
I think there is a misunderstanding
I'm sorry but i didn't sent anything (patch ,...) to you (or anyone
else) and I don't know anything about the
patch which Siegfried is talking about.
I've just noticed that there is a problem with xsl:include href path:
- this path can't be dynamic (due to xsl specification)
- the new turbine version (2.3.2) requires xsl paths to be servlet
content relative
The xsl included should be searched in the same (servlet relative) path
as the base xsl used
in turbine xsl transform method.
Raoul.
Eric Pugh wrote:
> Raoul,
>
> I know you sent me something, but I think I lost it, or couldn't get
> it working. I'll echo Siegfried and ask you to make sure it doesn't
> require TurbineServlet and we would happily apply it!
>
> ERic
>
> On Dec 30, 2005, at 2:40 PM, Siegfried Goeschl wrote:
>
>> Hi Raoul,
>>
>> +) it seems that the patch was applied TURBINE_2_3_BRANCH and not
>> the trunk - we should apply the path to the trunk
>> +) the patch can't be applied directly to Fulcrum since there is no
>> TurbineServlet and running in a servlet container is not mandatory
>> for Fulcrum /not even Turbine btw)
>>
>> Cheers,
>>
>> Siegfried Goeschl
>>
>> rc wrote:
>>
>>> Hi all,
>>>
>>> Thanks for help, but I would have prefered using turbine built-in
>>> services (easily upgradable)
>>>
>>> I think it's a bug that has to be corrected (when some of us have
>>> enough time), the more so as
>>> the new XSLtransformer class is more powerful (xsl parameters, ...).
>>>
>>> Any suggestions ?
>>>
>>> Bye
>>>
>>> Raoul
>>>
>>> Siegfried Goeschl wrote:
>>>
>>>> Hi Raoul,
>>>>
>>>> I implemented a cousin of XSLT service based on DOM4J - would this
>>>> be an option for you?
>>>>
>>>> Cheers,
>>>>
>>>> Siegfried Goeschl
>>>>
>>>> rc wrote:
>>>>
>>>>> Thomas Vandahl wrote:
>>>>>
>>>>>> Hi Raoul,
>>>>>>
>>>>>> this was a change of mine. The XSLT service of Turbine now uses
>>>>>> URLs and the ServletContext methods to access the .xsl-files.
>>>>>> This is a step to get Turbine to run from a .war-file.
>>>>>>
>>>>>> In your case I'd suggest to change the include path to an
>>>>>> absolute URL such as "http://somehost/xsl/tools.xsl" This should
>>>>>> fix the problem.
>>>>>>
>>>>>> Bye, Thomas.
>>>>>>
>>>>>
>>>>> Hi,
>>>>> I understand your objectives, but I can't use absolute constant
>>>>> url in my xsl include@href path. I can
>>>>> only use relatives or dynamic(servlet context) uris. But as you
>>>>> know, we can't use dynamic data inside include@href values.
>>>>>
>>>>> So, I'm always blocked on this point.
>>>>> By
>>>>>
>>>>> Raoul
>>>>>
>>>>>
>>>>>
>>>>> -------------------------------------------------------------------
>>>>> --
>>>>> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
>>>>> For additional commands, e-mail: turbine-user-
>>>>> help@jakarta.apache.org
>>>>>
>>>>>
>>>>
>>>> -------------------------------------------------------------------- -
>>>> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
>>>> For additional commands, e-mail: turbine-user- help@jakarta.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org