ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 34229] - Need ability to intercept calls to System.setSecurityManager() from embedded environment
Date Fri, 01 Apr 2005 02:01:33 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=34229>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=34229





------- Additional Comments From kevin.jackson@it.fts-vn.com  2005-04-01 04:01 -------
> Alternatively, we could try and set the security manager, catch the exception
> and back off from the attempt, opting to fork the jvm instead. 
I know that this kind of "catch a semi-expected exception and alter behaviour"
is used frequently in the code, but is there no other way?  I personally feel
that using exceptions as a flow control mechanism is a code smell.

I'd prefer an adapter approach mentioned in the report

just my opinion
Kev


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

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


Mime
View raw message