This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Deploying xsl sheets in Java Environment
- To: xsl-list at lists dot mulberrytech dot com
- Subject: Re: [xsl] Deploying xsl sheets in Java Environment
- From: Johannes Döbler <jd at aztecrider dot com>
- Date: Mon, 13 Aug 2001 17:42:10 +0200
- References: <F61ogxLDp7mvjkO22Zh00005ec6@hotmail.com>
- Reply-To: xsl-list at lists dot mulberrytech dot com
seems to be a little off topic for xsl-list, but here are some ideas:
Easy way: make the xsl file read-only (and additionally encrypt it by using
a lot of for-each instructions?)
Hard way: include the xsl file into your jar-file and then use
Class.getResourceAsStream() or ClassLoader.getResourceAsStream() to get a
inputstream to it and pass this stream to your xsl processor. The processor
will certainly have an initializer to read the stylesheet from a stream
instead of a file object.
Cheers,
Johannes
>Hi.
>
> > I need to deploy a xsl document that converts the input XML document into
> > another XML document that is used at the backend. One way of deploying
>this
> > xsl file is to place it in a config directory and access it from the Java
> > code. However, the config directory is deployed at the customer's server
> > site and I don't want the customers to be able to access this xsl file (to
> > avoid accidental deletes and changes)....What are my options? Is there a
>way
> > I can encrypt this file? I am not using any application server...
>
>For speed and obfuscation I guess you may complile a stylesheet into a java
>class. As far as I remember, alphaworks.ibm.com has a technology and so has
>the apache xml initiative. And many more.
>If this is ony to secure the stylesheet itself - not access to it, I guess
>it will be a right solution.
>
>Bye.
>/lexi
>
>
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list