[ http://issues.apache.org/jira/browse/XALANJ-2068?page=all ]
Brian Minchau updated XALANJ-2068:
----------------------------------
Fix Version: 2.7
(was: CurrentCVS)
> Xalan is too strict for codes running in a sandbox
> --------------------------------------------------
>
> Key: XALANJ-2068
> URL: http://issues.apache.org/jira/browse/XALANJ-2068
> Project: XalanJ2
> Type: Bug
> Components: Serialization
> Versions: CurrentCVS
> Reporter: Christine Li
> Assignee: Christine Li
> Priority: Minor
> Fix For: 2.7
> Attachments: Bug2068Patch.txt
>
> The original problem was reported by customer from Sun. "some people updated
> that variable in their code in order to run Xalan in a sandbox. Now that the
> variable cannot be updated, running Xalan in an unsigned applet is not
> possible anymore." Xalan should support the code that attempts to get the
> resource in a privileged block in order sidestep the problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
