Just thinking out lou about a possible workaround: Camel already provides the Exchange as a parameter to the XSL Transformer. Therefore you might be able to access the Exchange using an <xsl:param> from within your XSL transformation (remember the Exchange is POJO not a simple String or Java primitive, so it's up to the XSL engine how this gets handled).
Once you have the Exchange you can access the HttpServletRequest header as set by the Servlet component. (using the Exchange.HTTP_SERVLET_REQUEST as described on http://camel.apache.org/http). Finally you can use the HttpServletRequest inside your XSL to load the appropriate files. -- View this message in context: http://camel.465427.n5.nabble.com/xslt-component-and-URI-Resolver-tp3396685p3399434.html Sent from the Camel - Users mailing list archive at Nabble.com.
