If you do give Saxon 8.9 a try will you let us know how it turns out?

-jacobd

On 12/3/07, Wing Yew Poon <[EMAIL PROTECTED]> wrote:
> The problem with Saxon is that it makes non-backward-compatible
> API changes from one dot release to another (8.x to 8.y).
> XMLBeans 2.3.0 was tested with Saxon 8.8, so we know that it works
> with that version of Saxon. We cannot guarantee that it works with
> 8.9 if incompatible changes have been introduced in 8.9. Feel free
> to try it out, and if it works for you, fine, but you're on your
> own with that.
> - Wing Yew
>
> -----Original Message-----
> From: Willis Morse [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 03, 2007 7:26 AM
> To: [email protected]
> Subject: Re: Saxon, JAXP and classpath
>
>
> Answering my own question:
>
> > Question 4) If there's no way to use the JDK for the XSLT, then I
> > guess I need to figure out the Saxon XSLT problem. This same XSLT
> > run on the same source xml file works fine when executed in
> > StylusStudio using the embedded Saxon 8.9 library, and the built in
> > JDK xslt engine doesn't, either. So I'm left thinking that there's
> > some obscure Saxon initialization that's different between the way
> > StylusStudio sets up Saxon, and the way it's getting setup in my
> > app. Any thoughts?
>
> Saxon 8.8 has a known bug when running a transform to produce a DOM
> when using a default namespace:
>
>       https://sourceforge.net/tracker/index.php?
> func=detail&aid=1558133&group_id=29872&atid=397617
>
> This was fixed as a patch to 8.8, and is presumably fixed in Saxon 8.9.
>
> So the solution that I'm using is to add namespace prefixes to my
> result nodes in my xslt. When I do this, Saxon performs the transform
> properly.
>
> Moving to Saxon 8.9 might have also solved the problem, but the
> XMLBeans are so emphatic about only using 8.8 that I don't want to
> open this can of worms.
>
>
> - Willis Morse
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> Notice:  This email message, together with any attachments, may contain
> information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
> entities,  that may be confidential,  proprietary,  copyrighted  and/or
> legally privileged, and is intended solely for the use of the individual or
> entity named in this message. If you are not the intended recipient, and
> have received this message in error, please immediately return this by email
> and then delete it.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to