Is there any way to police what namespaces/xalan extensions are being
used in an xsl transform?
Ex, you have a jsp which does a transform for some of its rendering...
and you're letting 3rdParties write their own xml/xsl for that part of
the page...
Now, the xml and xsl is bundled in a JAR with any number of their own
java.classes...
I only want them to be able to access a single xalan extension of a
java.class that I wrote... and not let them call their own cause it
would be a *bit* of a security hole!
Any ideas??
Adam
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--