Re: Work on DBTags and XSL, release 2, and etcetera

["Kilian, Rex" <Re...@crowncastle.com>]

I'm trying to utilize the following on WebLogic 6.0:

<xtags:style xml="foo.xml" xsl="bar.xsl">
  <xtags:param name="foo" value="123"/>
  <xtags:param name="bar">456</xtags:param>
</xtags:style>

Is there a past version of the Xtags available that still supports the use
of the
<xtags:xalanStyle> tag?


-----Original Message-----
From: James Strachan 
Subject: Re: Work on DBTags and XSL, release 2, and etcetera 
Date: Wed, 13 Jun 2001 22:06:50 -0700 

Hi Morgan

From: "Morgan Delagrange" <mo...@apache.org>
> James, I haven't taken a close look at XTags yet, but what would
> you say to working on XSL, release 2 together and pointing XTags users
> XSL.  Or maybe we could bundle them together?  It seems like we could gain
> more momentum together.

XTags started life as being an implementation of XSLT in JSP custom tags,
allowing JSP and JSP custom tags to be used 'inside' XSLT so to speak. So it
initially focussed on parsing documents then using XPath to navigate and
style XML.

For various reasons XTags gradually expanded to integrate full XSLT support
as well. (e.g. you can parse a document, iterate over it using XPath then
style part of it using a regular XSLT operation).

Currently the <xtags:style> tag implements XSLT in a similar manner to the
<xsl:apply> tag and allows parameters to be passed in with <xtags:param>.
Its currently based on JAXP 1.1 and can take a local resource URI, a URL, a
DOM node, a dom4j Node or the text body for the XML or XSL. It can also take
the current context too. So the following is possible...

    <xtags:parse url="http://foo.com/user.xml"/>
    Hello there <xtags:valueOf select="/user/name"/>
    <%-- now style the whole document with XSLT --%>
    <xtags:style xsl="userAsHtml.xsl"/>

I 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 aorund and can be removed when all common Servlet engines can handle
JAXP1.1


So in summary I'd say my preference is to merge all XML operations and
features into the same library if at all possible. Though this could confuse
new users as there are already quite a few tags in XTags, so maybe a small
'XSLT only' library with just a few tags and then a full 'XPath and XSLT'
library with many more tags might make sense?

Thoughts?

James

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>