On Wed, 2009-08-19 at 14:32 +0300, Sjur Moshagen wrote: > Den 19. aug. 2009 kl. 10.50 skrev Sjur Moshagen: > > > Den 19. aug. 2009 kl. 09.23 skrev Brian M Dube: > > > >>> Any idea on how to make the protocol 'known' to the xsl processor in > >>> Cocoon? > >> > >> I've been down this path once before. There is a Jira issue > >> (somewhere; sorry, I'm just on the way to sleep) about rewriting the > >> imports. I never had success with it. I'll look for that issue and > >> any > >> notes I may have. > > > > It is in: > > > > https://issues.apache.org/jira/browse/FOR-1000 > > > > But according to: > > > > http://www.mail-archive.com/u...@forrest.apache.org/msg02743.html > > (Thorsten Scherler) > > > > it should work. I'll continue the investigation. > > It seems to be used in dispatcher, in at least the following file: > > whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/ > resources/stylesheets/helper/variable.helper.xsl: > > <xsl:stylesheet version="1.0" > xmlns:forrest="http://apache.org/forrest/properties/1.0"; > xmlns:xsl="http://www.w3.org/1999/XSL/Transform";> > <xsl:import href="lm://transform.xml.dotdots"/> > <xsl:import href="lm://transform.xml.pathutils"/> > ... > > The dotdots LM string matches in one of the main locationmaps, and > should resolve just fine. That is, when using dispatcher, using an lm: > protocol in an xsl import seems to work just fine. > > The question is then: why doesn't it work in all other cases?
It should work fine everywhere. Make sure the resources are exposed via the locationmap. salu2 > > Best regards, > Sjur > -- Thorsten Scherler <thorsten.at.apache.org> Open Source <consulting, training and solutions>
