At 02:41 PM 11/12/01 +0000, you wrote: >Is there anyway that the XSP page can be told to treat the response as XHTML (and >build a XML Fragment)? > >Thanks for any advice, > >Jason Cunningham
Yes. Someone else had this same problem recently. Use <util:include-expr>. It will parse the text that you pass in to it, and generate SAX calls from it (as opposed to writing the text straight to the output - after escaping all the control chars - like it's doing now). 1) Include the namespace xmlns:util="http://apache.org/xsp/util/2.0"; in your XSP or the <util:include-expr> won't get called properly. 2) the call you need to make this work: <util:include-expr><util:expr>your xml goes here</util:expr></util:include-expr> or <xsp:logic>String s = <get xml from somewhere>;</xsp:logic> <util:include-expr><util:expr><xsp:expr>s</xsp:expr></util:expr></util:include-expr> <xsp:expr>s</xsp:expr> takes the value of String s, which is then passed in to <util:include-expr>. DR --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
