You are viewing a plain text version of this content. The canonical link for it is here.
Posted to announcements@xml.apache.org by Shane Curcuru <sh...@yahoo.com> on 2003/10/14 15:11:20 UTC
[ANN] XML-Commons Resolver component 1.1b1 beta build released
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The xml-commons team is pleased to announce a beta release of our
popular Resolver component version 1.1b1 (beta before a 1.1 release).
The release is available at
http://www.apache.org/dyn/closer.cgi/xml/commons/
Blurb
- -----
Resolver
(http://xml.apache.org/commons/components/resolver/index.html) is a
catalog-based XML Entity and URI resolver suitable for plugging into
your XML tools. It supports several popular catalog formats.
XML-Commons is a subproject devoted to XML Standards-related code and
components, and also hosts the Which utility and xml-apis.jar, which
implements JAXP.
Status
- ------
Resolver 1.1b1 is a beta release in preparation for a 1.1 release in
the very near future. It incorporates a number of minor bugfixes as
well as some new functionality requested by the Ant team. Note that
some of the APIs in 1.1 are not backwards-compatible with the 1.0
release, so if you're a previous user please read the release notes
carefully.
This release is built from code tagged xml-commons-resolver-1_1_b1 in
CVS.
The full list of changes for 1.1x is viewable at:
http://xml.apache.org/commons/components/resolver/resolver-release-not
es.html
Please send feedback to commons-dev@xml.apache.org (after
subscribing).
The Apache xml-commons team
P.S. Astute readers will note that the release was actually made last
week, and silly Shane forgot to send out this email until Stefan
reminded him... sorry!
-----BEGIN PGP SIGNATURE-----
Version: PGP Personal Security 7.0.3
iQA/AwUBP4v1qTLsF1kwoh1VEQIOdgCePaBL3HElnyy+6RnL5K1wv4X/ZmMAoPn9
CVv72V1obDUfQJPTcq/vD4+H
=6cKn
-----END PGP SIGNATURE-----
Re: [ANN] XML-Commons Resolver component 1.1b1 beta build released
Posted by Stefan Bodewig <bo...@apache.org>.
Thanks Shane ;-)
On Tue, 14 Oct 2003, Shane Curcuru <sh...@yahoo.com> wrote:
> The release is available at
> http://www.apache.org/dyn/closer.cgi/xml/commons/
Why don't you point to <http://xml.apache.org/mirrors.cgi> instead?
Stefan
Re: [ANN] XML-Commons Resolver component 1.1b1 beta build released
Posted by Tetsuya Kitahata <te...@apache.org>.
Congratulations,
Shane and Apache Commons-XML team!
Please see,
http://jakarta.apache.org/site/elsewhere.html#20031014.1
... :-)
Best Regards,
-- Tetsuya. (tetsuya@apache.org)
On Tue, 14 Oct 2003 09:11:20 -0400
(Subject: [ANN] XML-Commons Resolver component 1.1b1 beta build released)
Shane Curcuru <sh...@yahoo.com> wrote:
> The xml-commons team is pleased to announce a beta release of our
> popular Resolver component version 1.1b1 (beta before a 1.1 release).
> The release is available at
> http://www.apache.org/dyn/closer.cgi/xml/commons/
>
> Blurb
> - -----
> Resolver
> (http://xml.apache.org/commons/components/resolver/index.html) is a
> catalog-based XML Entity and URI resolver suitable for plugging into
> your XML tools. It supports several popular catalog formats.
> XML-Commons is a subproject devoted to XML Standards-related code and
> components, and also hosts the Which utility and xml-apis.jar, which
> implements JAXP.
>
> Status
> - ------
>
> Resolver 1.1b1 is a beta release in preparation for a 1.1 release in
> the very near future. It incorporates a number of minor bugfixes as
> well as some new functionality requested by the Ant team. Note that
> some of the APIs in 1.1 are not backwards-compatible with the 1.0
> release, so if you're a previous user please read the release notes
> carefully.
>
> This release is built from code tagged xml-commons-resolver-1_1_b1 in
> CVS.
>
> The full list of changes for 1.1x is viewable at:
>
>
> http://xml.apache.org/commons/components/resolver/resolver-release-not
> es.html
>
> Please send feedback to commons-dev@xml.apache.org (after
> subscribing).
>
>
> The Apache xml-commons team
>
> P.S. Astute readers will note that the release was actually made last
> week, and silly Shane forgot to send out this email until Stefan
> reminded him... sorry!
---------------------------------------------------------------------
Tetsuya Kitahata -- Terra-International, Inc.
E-mail: tetsuya@apache.org http://www.terra-intl.com/
Apache Software Foundation Committer: http://www.apache.org/~tetsuya/
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
RE: [ANN] XML-Commons Resolver component 1.1b1 beta build released
Posted by Robert Koberg <ro...@koberg.com>.
Hi,
I would like to use this resolver, but was wondering how to handle the
situation described below. There is also a bug or at least a serious
inconsistency in how Xalan-J and Xalan XSLTC handles URI resolution. I have
posted the info on both the Xalan and XSL lists but can't get someone from
Xalan to comment.
-----
Overview:
According to most API's you can set a URIResolver on the TransformerFactory
and one on the Transformer. Generally, the resolver set on the
TransformerFactory resolves xsl:includes and xsl:imports. If set on the
Tranformer it resolves document() function calls.
-----
The bug:
- standard xalan requires you to set a URIResolver on the TransformerFactory
for xsl:include and xsl:import and set one on the Transformer for document()
- xsltc xalan uses the TransformerFactory for both xsl:include/xsl:import
and document() -- you cannot set a resolver on the Transformer for
document(), like the standard xalan.
--
FYI:
- Saxon allows you to set a resolver on the TransformerFactory to resolve
both includes/imports and document().
It also lets you set one for the factory and one for the transformer. When
this is done the factory resolves include/import and the transformer
resolves document(). This is the best way, because, in IMHO, you get the
Transformer from the factory, so if you don't set one on the Transformer it
defaults to the one set on the factory.
-----
The situation:
I have a webapp that needs different resolution for xsl:include depending on
the thing/view/action they are doing in the app (e.g. preview, edit,
generate for a CMS). I need the same resolution for the document function
for all views (i.e. the client's actual XML content).
Is it possible to set the different catalogs for the TransformerFactory and
the Transformer for the same transformation?
If so, does it work for both the standard xalan and xsltc?
Thanks for any info,
-Rob
p.s. I am not currently on the commons-dev. Is that the best place to
continue this?
RE: [ANN] XML-Commons Resolver component 1.1b1 beta build released
Posted by Robert Koberg <ro...@koberg.com>.
Hi,
I would like to use this resolver, but was wondering how to handle the
situation described below. There is also a bug or at least a serious
inconsistency in how Xalan-J and Xalan XSLTC handles URI resolution. I have
posted the info on both the Xalan and XSL lists but can't get someone from
Xalan to comment.
-----
Overview:
According to most API's you can set a URIResolver on the TransformerFactory
and one on the Transformer. Generally, the resolver set on the
TransformerFactory resolves xsl:includes and xsl:imports. If set on the
Tranformer it resolves document() function calls.
-----
The bug:
- standard xalan requires you to set a URIResolver on the TransformerFactory
for xsl:include and xsl:import and set one on the Transformer for document()
- xsltc xalan uses the TransformerFactory for both xsl:include/xsl:import
and document() -- you cannot set a resolver on the Transformer for
document(), like the standard xalan.
--
FYI:
- Saxon allows you to set a resolver on the TransformerFactory to resolve
both includes/imports and document().
It also lets you set one for the factory and one for the transformer. When
this is done the factory resolves include/import and the transformer
resolves document(). This is the best way, because, in IMHO, you get the
Transformer from the factory, so if you don't set one on the Transformer it
defaults to the one set on the factory.
-----
The situation:
I have a webapp that needs different resolution for xsl:include depending on
the thing/view/action they are doing in the app (e.g. preview, edit,
generate for a CMS). I need the same resolution for the document function
for all views (i.e. the client's actual XML content).
Is it possible to set the different catalogs for the TransformerFactory and
the Transformer for the same transformation?
If so, does it work for both the standard xalan and xsltc?
Thanks for any info,
-Rob
p.s. I am not currently on the commons-dev. Is that the best place to
continue this?
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org