Ignore last: Saxon Servlet XSLT Version 2.0 Implementa

Sorry for last, I just found out I am using Resin and Saxon doesn't support
it!

Gary

> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Gary
> Cornelius
> Sent: 28 May 2003 09:29
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject:  Saxon Servlet XSLT Version 2.0 Implementation Problem
>
>
> Hi,
>
> I have been trying to test XSLT version 2.0 with the saxon
> serlvet code. My
> problem is that the servlet code only appears to run version 1.0 syntax
> trouble free and actually complains about almost all version 2.0
> syntax.  My
> set up is as follows...
>
> 1. My URL access
> /saxon/servlet/SaxonServlet?source=books.xml&style=books.xsl
>
> 2. Files uploaded to my web host
> + webapps
>   + saxon
>     - books.xsl
>     - books.xml
>     + WEB-INF
>       + lib
>         - saxon7.jar
>         - saxon7-jdom.jar
>         - saxon7-sql.jar
>       + classes
>         - SaxonServlet.java
>         - SaxonServlet.class
>       + tmp
>       + work
>
> In order to run my version 2.0 syntax I am not sure whether I
> need to amend
> the servlet code I have in some way, or ask my web host to change some of
> their settings that are conflicting with my implementation. Can
> anyone help?
>
> Cheers
>
> Gary
>
> PS  Also, some people have mentioned that implementing the
> servlet can be a
> security risk because people can execute their own xslt using it...
> possibly, with evil xslt extension functions that eMail rude mail and wipe
> the server hard drive, does anyone know of an easy way to protect against
> this?
>
>
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to which
> they are addressed. If you have received this email in error
> please reply to this email and then delete it. Please note that
> any views or opinions presented in this email are solely those of
> the author and do not necessarily represent those of Future.
>
> The recipient should check this email and any attachments for the
> presence of viruses. Future accepts no liability for any damage
> caused by any virus transmitted by this email.
>
> Future may regularly and randomly monitor outgoing and incoming
> emails and other telecommunications on its email and
> telecommunications systems. By replying to this email you give
> your consent to such monitoring.
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>


This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please reply to this email and then delete it. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Future. 

The recipient should check this email and any attachments for the presence of viruses. Future accepts no liability for any damage caused by any virus transmitted by this email. 

Future may regularly and randomly monitor outgoing and incoming emails and other telecommunications on its email and telecommunications systems. By replying to this email you give your consent to such monitoring.

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list