x:tranform difficultiessssss

[RAYMOND Romain <ro...@c-s.fr>]

Hello,

is this the correct " syntax " to realize an xslt transformation :
"
	<c:import url="/xml/my.xml" var="xml" />
	<c:import url="/xslt/my.xsl" var="xslt" />
        <x:transform xmlUrl="${xml}" xsltUrl="${xslt}"/>
"


thanks.

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

Re: x:tranform difficultiessssss

[Shawn Bayern <ba...@essentially.net>]

On Wed, 17 Apr 2002, RAYMOND Romain wrote:

> Any indications about setting an URIResolver related ro the called
> transformer ...

Yes.  The spec's now accepts 'xmlSystemId' and 'xsltSystemId' attributes
for <x:transform>, and I've implemented a URIResolver in our
implementation to resolve entities appropriately through
ServletContext.getResource().

I also use an EntityResolver for the parsing phase for both the XML and
XSLT documents.  The code is much more complex than I expected, since we
have to maintain more control over the parsing than TrAX wants to give us.
But I've tested it, and it does seem to work in every case I can think of
(context-relative, page-relative, absolute systemIds, and root-relative
versus page-relative entity href paths in the URIResolver itself, for such
things as <xsl:import>, <xsl:include>, and document()).

The CVS head has been updated; the changes will also be reflected in the
nightly build and Beta2.

-- 
Shawn Bayern
Author, "JSP Standard Tag Library"  http://www.jstlbook.com
(coming this summer from Manning Publications)


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

Re: x:tranform difficultiessssss

[RAYMOND Romain <ro...@c-s.fr>]

Any indications about setting an URIResolver related ro the called
transformer ...

Shawn Bayern a écrit :
> 
> On Wed, 17 Apr 2002, RAYMOND Romain wrote:
> 
> > is this the correct " syntax " to realize an xslt transformation :
> > "
> >       <c:import url="/xml/my.xml" var="xml" />
> >       <c:import url="/xslt/my.xsl" var="xslt" />
> >         <x:transform xmlUrl="${xml}" xsltUrl="${xslt}"/>
> 
> No, that never was; it's something of a hypbrid between the two different
> usages we've waffled between, so the confusion is certainly
> understandable.  :-)
> 
> The code as it is right now in the archive (but not in yesterday's nightly
> build) will support the Proposed Final Draft's usage:
> 
>         <c:import url="/xml/my.xml" var="xml" />
>         <c:import url="/xslt/my.xsl" var="xslt" />
>         <x:transform xml="${xml}" xslt="${xslt}"/>
> 
> This will show up in future nightly builds and in the Beta2 release.
> 
> --
> Shawn Bayern
> Author, "JSP Standard Tag Library"  http://www.jstlbook.com
> (coming this summer from Manning Publications)

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

Re: x:tranform difficultiessssss

[Shawn Bayern <ba...@essentially.net>]

On Wed, 17 Apr 2002, RAYMOND Romain wrote:

> is this the correct " syntax " to realize an xslt transformation :
> "
> 	<c:import url="/xml/my.xml" var="xml" />
> 	<c:import url="/xslt/my.xsl" var="xslt" />
>         <x:transform xmlUrl="${xml}" xsltUrl="${xslt}"/>

No, that never was; it's something of a hypbrid between the two different
usages we've waffled between, so the confusion is certainly
understandable.  :-)

The code as it is right now in the archive (but not in yesterday's nightly
build) will support the Proposed Final Draft's usage:

 	<c:import url="/xml/my.xml" var="xml" />
 	<c:import url="/xslt/my.xsl" var="xslt" />
        <x:transform xml="${xml}" xslt="${xslt}"/>

This will show up in future nightly builds and in the Beta2 release.

-- 
Shawn Bayern
Author, "JSP Standard Tag Library"  http://www.jstlbook.com
(coming this summer from Manning Publications)


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