Hi again, There are a couple of ways to keep this type of thing application nuetral:
1. create a Node object and pass that into the Transform. For example: Node root = null; try { DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance(); factory.setNamespaceAware(true); DocumentBuilder docbuilder = factory.newDocumentBuilder(); org.w3c.dom.Document outNode = docbuilder.newDocument(); root = docbuilder.parse(new InputSource(new StringReader(restrictions.toString()))); } catch (Exception e) { System.out.println(e); } 2. use something like <xsl:apply-templates select="document($get.my.string.uid)"/> to retrieve the string which comes back as a nodeset. best, -Rob > -----Original Message----- > From: Ryan Agler [mailto:ryanagler@;hotmail.com] > Sent: Thursday, October 24, 2002 8:11 AM > To: [EMAIL PROTECTED] > Subject: RE: [Off-topic:XSLT] Passing an XML fragment via a HTML form. > > > Yes, I use that exact same technique (hidden textareas). To get the > parameter back as XML, I wrote an XSP that grabs the request parameter > XML string, turns it into a DOM document, and then iterates through the > DOM nodes to emit corresponding SAX events. Now my Java isn't the best > in the world, there is probably a better way, but it works for me. > > -----Original Message----- > From: ROSSEL Olivier [mailto:olivier.rossel@;airbus.com] > Sent: Thursday, October 24, 2002 4:06 AM > To: '[EMAIL PROTECTED]' > Subject: RE: [Off-topic:XSLT] Passing an XML fragment via a HTML form. > > > It will work for a textarea if that is an option, but for an > > input, all the tags get stripped out and just the content > > gets included. > > This is a very interesting thread. > So with hidden textareas or you custom class, I can pass the XML > fragment. > But when receiving the request parameter in my XSL, how can I transform > it > into a XML fragment again and out put it of the transformation? > Is the noddeset() function useful in that case? > > This e-mail is intended only for the above addressee. It may contain > privileged information. If you are not the addressee you must not copy, > distribute, disclose or use any of the information in it. If you have > received it in error please delete it and immediately notify the sender. > Security Notice: all e-mail, sent to or from this address, may be > accessed by someone other than the recipient, for system management and > security reasons. This access is controlled under Regulation of > Investigatory Powers Act 2000, Lawful Business Practises. > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> > > To unsubscribe, e-mail: <[EMAIL PROTECTED]> > For additional commands, e-mail: <[EMAIL PROTECTED]> > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> > > To unsubscribe, e-mail: <[EMAIL PROTECTED]> > For additional commands, e-mail: <[EMAIL PROTECTED]> > --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>