You achieve this typically by putting a condition in your epilogue, for example:
<p:processor uri="oxf/processor/request">
<p:input name="config">
<config>
<include>/request/path-info</include>
<include>/request/parameters/parameter</include>
</config>
</p:input>
<p:output name="data" id="request"/>
</p:processor><p:choose href="#request">
<p:when
test="/request/parameters/parameter[name = 'form/print']/value = 'true'">
<p:processor uri="oxf/processor/xslt">
<p:input name="data" href="#data"/>
<p:input name="config" href="oxf:/themes/print-theme.xsl"/>
<p:output name="data" id="data-with-theme"/>
</p:processor>
</p:when>
<p:otherwise>
<p:processor uri="oxf/processor/xslt">
<p:input name="data" href="#data"/>
<p:input name="config" href="oxf:/themes/regular-theme.xsl"/>
<p:output name="data" id="data-with-theme"/>
</p:processor>
</p:otherwise>
</p:choose>-Erik
bill french wrote:
> hello, > > is there any way to exclude pages specified in the controller from the > epilogue's final pass? one of the pages in our app has a "print view" > corresponding to a completely different css and layout. we don't want > the epilogue to interfere with that page. > > thanks, > > --bill
_______________________________________________ oxf-users mailing list [EMAIL PROTECTED] http://mail.orbeon.com/mailman/listinfo/oxf-users
