[jira] Updated: (XALANJ-2068) Xalan is too strict for codes running in a sandbox

["Brian Minchau (JIRA)" <xa...@xml.apache.org>]

     [ http://issues.apache.org/jira/browse/XALANJ-2068?page=history ]

Brian Minchau updated XALANJ-2068:
----------------------------------

        reviewer: minchau@ca.ibm.com
    fix-priority: fp3

Update the issue to have Brian Minchau as the reviewer, once there is a patch.

> 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

>
> 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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org