<quote who="Ryan Hoegg"> > Hello, > > I am not absolutely sure I understand your architecture.
It is harder to explain than it is in real life ;o) Think; Independent networked XML resources where the type of each resource is unknown until the response document is returned. BUT that each document type has an installed set of XSL stylesheet for transformations in Cocoon. > Yes, XSLT is namespace aware. You can define namespaces prefixes for > your namespaces in your stylesheet and match that way. However, I think > you can also do this: <xsl:template > xmlns:fooBar="http://www.foo.com/bar/1.0"; > match="fooBar:baz"><xsl:apply-templates/></xsl:template> Would someone > else more steeped in XSLT knowledge than I verify this? Wow... Is this so?? I assume I could have the xmlns declaration at the root node as well, right? I also assume then, that the document node <foo:mynode xmlns:foo="http://www.mycompany.com/mytype"; > </foo:mynode> would be matched by the template <xsl:template xmlns:bar="http://www.mycompany.com/mytype"; match="bar:mynode" /> Really good stuff if this works. Will try later! > Sounds like a custom Transformer to me. I think you could set a > pipeline parameter in your Generator denoting which Block this document > is from and then have a lookup facility in your Transformer that applies > the correct stylesheet for that Block. If was thinking of the generator creating a PI with the "type" for the transformer to use. The sheer size of the TraxTransformer gave me a creepy feeling and I didn't want to extend it. > Hope this helps, YES, it really does. Thanks a lot! Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
