Hi, > -----Original Message----- > From: Hunsberger, Peter [mailto:[EMAIL PROTECTED]] > Sent: Friday, October 04, 2002 9:34 AM > To: '[EMAIL PROTECTED]' > Subject: RE: XML input module (was: RE: Nice changes!) > > > > > Maybe, maybe not. One would need to use a lot extension functions to > > > achieve similar things (e.g. j2ee, databases and stuff) but that might > > > be portable to other pipeline systems (?). OTOH Apache Cocoon a lot > > > about SoC and it will need to be seen if that works as well with your > > > suggested approach. > > > > Instead of extensions you could use custom URIResolvers to return the > result > > from anywhere (or just do something and return succes/fail) to an > representation > > usable by a transformation. > > That would work, but where I'm heading I essentially want the equivalent of > a uri-resolver to be coded using XSLT looking not only at the URI but also > the current context.
in XSLT 1.0 you can do: <xsl:apply-templates select="document($util_function, $client_site)"/> Where you pass the href and base arguments to the resolver. The 2cnd arg being the context. best, -Rob --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
