Re: external XSLT failing

[Erik Bruchez]

The two constructions are equivalent. You just have to be careful about 
namespace declarations when you inline / outline a stylesheet into / from a 
pipeline. Besides that, this must definitely be working! If you cannot figure 
it out, please let us know. I guess an example input document would help 
reproduce the issue.

-Erik

Bob Daly wrote:

The following works as expected when called directly in an XPL:
        <p:processor uri="oxf/processor/xslt">
                <p:input name="data" href="#retrieval-parms"/>
                <p:input name="config">
                        <xsl:stylesheet 
xmlns:xsl="http://www.w3.org/1999/XSL/Transform";
version="1.0"
xmlns:padlmsg="urn:publicid:IDN+cde.berkeley.edu:padlmsg:200403:en";>
                                <xsl:template match="/form">
                                        <xsl:variable name="method" select="./method"/>
                                        <xsl:variable name="queryVal" 
select="./queryVal"/>
                                        <config>
                                                <url>
                                                        <xsl:value-of 
select="./destination"/>
                                                </url>
                                                <namespace>
                                                        <prefix>padl</prefix>
                                                        
<nsuri>urn:publicid:IDN+cde.berkeley.edu:schema:bxd:padl:200402:en</nsuri>
                                                </namespace>
                                                <namespace>
                                                        <prefix>padlmsg</prefix>
                                                        
<nsuri>urn:publicid:IDN+cde.berkeley.edu:padlmsg:200403:en</nsuri>
                                                </namespace>
                                                <msgbody>
                                                        <padlmsg:msgbody>
                                                                <padlmsg:appid>
                                                                        <xsl:value-of 
select="./relyingAppID"/>
                                                                </padlmsg:appid>
                                                                <xsl:choose>
                                                                        <xsl:when 
test="$queryVal != ''">
                                                                                <padlmsg:query 
method="{$method}">
                                                                                        
<xsl:value-of select="$queryVal"/>
                                                                                
</padlmsg:query>
                                                                        </xsl:when>
                                                                        <xsl:otherwise>
                                                                                <padlmsg:query 
method="{$method}"/>
                                                                        
</xsl:otherwise>
                                                                </xsl:choose>
                                                        </padlmsg:msgbody>
                                                </msgbody>
                                        </config>
                                </xsl:template>
                        </xsl:stylesheet>
                </p:input>
                <p:output name="data" id="service-config" debug="service-conf"/>
        </p:processor>
The same exact XSLT in its own .xslt file, called within the pipeline
like this, FAILS:
        <p:processor uri="oxf/processor/xslt">
                <p:input name="data" href="#retrieval-parms"/>
                <p:input name="config"
href="oxf:/app/transforms/messageTemplates/PADL/PADLRetrieval.xslt"/>
                <p:output name="data" id="service-config" debug="service-confg"/>
        </p:processor>
The output is a null document.

I can provide more info if needed, but this is a very simple thing I'm
trying to do and it's not working - this has always worked for me in the
past with older versions of OXF.
-Bob Daly
_______________________________________________
oxf-users mailing list
[EMAIL PROTECTED]
http://mail.orbeon.com/mailman/listinfo/oxf-users