This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Saxon6.0.2: user written extensions
- From: Xiaocun Xu <xiaocunxu at yahoo dot com>
- To: xsl-list at lists dot mulberrytech dot com
- Date: Fri, 18 Jan 2002 12:36:58 -0800 (PST)
- Subject: RE: [xsl] Saxon6.0.2: user written extensions
- Reply-to: xsl-list at lists dot mulberrytech dot com
Yeah, I would very much wish to upgrade to a newer
release. But due to we still use Xerces1.2.0 and that
it is incomptiable with newer Saxon (in particular
Saxon6.4.3 which I tried), it would require the
upgrade of Xerces from 1.2.0 to 1.4.4. Given the
aggressive release schedule we have, we just don't
have the time to do all of these before I implement
this functionality: attribute name mapping.
Unfortunely I no longer can find a full download of
Saxon6.0.2 including documentation. I was able to dig
out a full download of Saxon5.5.1 and found the
document extensibility.html dated 7/24/00. Is this
applicable to Saxon6.0.2? If I go with this approach,
how difficult would it be to migrate to a later Saxon
release such as 7.0?
Besides extension function and template, what other
alternatives I may have?
Much thanks,
Xiaocun
--- Michael Kay <michael.h.kay@ntlworld.com> wrote:
> Yes, it's possible to write user-written extension
> functions (in Java) using
> releases of Saxon well before 6.0.2, see the
> extensibility.html file for
> details. But it's a very old release, please don't
> expect any help. But I do
> think you would find it worth your while to use a
> newer release.
>
> Mike Kay
>
> > -----Original Message-----
> > From: owner-xsl-list@lists.mulberrytech.com
> > [mailto:owner-xsl-list@lists.mulberrytech.com]On
> Behalf Of Xiaocun Xu
> > Sent: 18 January 2002 14:02
> > To: xsl-list
> > Subject: [xsl] Saxon6.0.2: user written extensions
> >
> >
> > Hi,
> >
> > I am interested to implement Jeni's
> recommendation
> > for attribute name mapping via mapping XML (Re:
> [xsl]
> > change a list of attribute name). I thought the
> most
> > efficient way to handle this would be through user
> > written extension functions.
> > The situation I have right now is our
> application
> > currently uses Saxon6.0.2 (started to use a year
> ago)
> > and Xerces1.2.0. I tried to upgrade to
> Saxon6.4.3,
> > but that had collision with Xerces1.2.0 (which I
> had
> > to put Saxon6.4.3 in front of Xerces1.2.0 in the
> > classpath to get around). We probably won't have
> time
> > to upgrade both to Saxon6.4.3 and Xerces1.4.4
> until
> > the next major release.
> > With my current situation, is it possible to
> write
> > user written extension functions? If not, the
> only
> > alternative is via templates?
> >
> > Much thanks,
> > Xiaocun
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Send FREE video emails in Yahoo! Mail!
> > http://promo.yahoo.com/videomail/
> >
> > XSL-List info and archive:
> http://www.mulberrytech.com/xsl/xsl-list
> >
>
>
> XSL-List info and archive:
> http://www.mulberrytech.com/xsl/xsl-list
>
__________________________________________________
Do You Yahoo!?
Send FREE video emails in Yahoo! Mail!
http://promo.yahoo.com/videomail/
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list