Do you have to stick on WL 6.0. I think they patched 6.1 so that it could support JAXP1.1, which is pretty much a requirement for most XML processing tools these days.
Or if you want a non-JAXP version of <xtags:style>, you could try the old <xtags:xalanStyle> tag. To get this tag do a CVS checkout of XTags using the CVS tag 'non-JAXP-support' James ----- Original Message ----- From: "Kilian, Rex" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, June 06, 2002 12:51 AM Subject: xtags:style with xtags:param on WebLogic 6.0 > I'm trying to do XSLT transformation and pass in parameters on WebLogic 6.0. > Utilizing the XSL taglib the following does work but the tag does not > support parameters. > > <xsl:apply xml="foo.xml" xsl="bar.xsl"/> > > Utilizing the Xtags taglib and using the xalan-2.0.1.jar file to overcome > the "java.lang.NoClassDefFoundError: javax/xml/transform/URIResolver" error > I was able to do the following to parse and output the XML. > > <xtags:parse id="data" uri="foo.xml"/> > <xtags:output method="html" indent=" "> > <xtags:copyOf select="ROOT_NODE"/> > </xtags:output> > > However I notice this message in the log file when the code for the tag was > implemented - "Warning: Error occurred using JAXP to load a SAXParser. Will > use Aelfred instead". > Moving on I tried to use <xtags:style> for the transformation > > <xtags:style xml="foo.xml" xsl="bar.xsl"/> > > I get this error - "System property org.xml.sax.driver not specified" which > lead to a modification in the properties file of WebLogic - > "-Dorg.xml.sax.driver=org.apache.xerces.parsers.SAXParser". > With this in place the following error is returned: > > java.lang.NoSuchMethodError > at org.apache.xpath.axes.ChildWalkerMultiStep.getNextNode() > > At this point I tried to use the <xtags:xalanStyle> tag based on the > recommendation from > [http://www.mail-archive.com/taglibs-dev@jakarta.apache.org/msg01116.html] > > "... had problems on a recent project using JAXP 1.1 inside WebLogic (WL 6.0 > SP1 can only use JAXP 1.0) so as a workaround I added <xtags:xalanStyle> > which behaves just like <xtags:style> except it explicitly uses the Xalan > API directly rather than JAXP 1.1. Hopefully this will be just a temporary > work around and can be removed when all common Servlet engines can handle > JAXP1.1" > > and from > [http://www.mail-archive.com/taglibs-dev@jakarta.apache.org/msg01702.html] > > "Currently it maintains backwards compatibility with servlet engines that > cannot support JAXP 1.1 such as WebLogic 6.0 via the <xtags:xalanStyle> tag. > This requires the xalanj1compat.jar from the Xalan 2 distribution. This tag > will be deprecated once we have some stable releases available." > > However the <xtags:xalanStyle> tag is no longer specified within the TLD so > I am assuming is has been removed from the Xtags distribution. > > Is there a past version of Xtags available that still supports the use of > the <xtags:xalanStyle> tag? > > Is there another way to achieve the end result? I even researched the JSTL > for <x:transform> and <x:param> but WebLogic 6.0 does not support the JSP > 1.2 specifications. > > > > > > > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>