You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by bu...@apache.org on 2002/01/12 17:10:42 UTC

DO NOT REPLY [Bug 5816] - SecurityExceptions not reported/ newTransformer newTemplates dont return

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5816>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5816

SecurityExceptions not reported/ newTransformer newTemplates dont return

curcuru@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|javax.xml                   |org.apache.xalan.client
            Summary|SecurityExceptions not      |SecurityExceptions not
                   |reported/ newTransformer    |reported/ newTransformer
                   |newTemplates dont return    |newTemplates dont return



------- Additional Comments From curcuru@apache.org  2002-01-12 08:10 -------
- Could you attach a code sample of what your applet does?  We really need to see what you mean when you say 'following code is ignored'
- A while back we explicitly added a bunch of try ... catch(SecurityException)... blocks specifically for the applet case: in many cases, we're trying to read a property or load a file.  In some cases, there wasn't an obvious fallback, so there might be a case where we treat the catch as a no-op where we should really be doing something else.  We need a clear use case to fix this though with some specific instructions on what to do inside the catch.