Ok, this is probably the completely wrong way to do it. So I look forward to the gentle correction. O
I'd like to use one xsp as my 'controller' and have it decide what to do based on some action. That action returns xml as its result. I then want the controller to pick the appropriate 'view' based on what the action was and maybe a return code. I'd like that 'view' to be an xsl that is first in the pipeline before any other PI's that might already exist for that xsp. Any way of doing that? I can't seem to see any way of defining a PI to work in Axkit dynamically from within the xsp. I tried a bunch of different things but usually something like: <xsp:pi target="xml-stylesheet"> <xsl:attribute name="href">my.xsl</xsl:attribute> <xsl:attribute name="type">text/xsl</xsl:attribute> </xsp:pi> or I saw somewhere <xsp:pi target="xml-stylesheet">"href=my.xsl, type=text/xsl"</xsp:pi> I couldn't really find any documentation on it that had any examples of what I'm trying to do. Which always makes me suspect I'm trying to do The Wrong Thing. But in some cocoon stuff it sounded like that was supposed to work? Anyhow... One alternative is to use AddAxkitRootProcessors for a given xml root tag and then wrap some arbitrary xml element to trigger the right xsl. But that feels wrong. (also, doesn't that work only against the root element? So if I have an xsp I would have already defined the root and couldn't dynamically name it anyway). So I'm left with making an xsp per each action and then specifying (hardcoded-ly) in the top of the xsp the xsl I want it to be rendered with first. But of course that still doesn't give me the dynamic thing I'm looking for. I feel like I'm simply missing something here. Is there some easy way to do what I'm trying to do? Thanks! Ken. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
