PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=919
*** shadow/919 Wed Jun 13 12:20:06 2001
--- shadow/919.tmp.29397 Fri Aug 3 07:21:18 2001
***************
*** 2,9 ****
| Double Check Locking scheme will not work! |
+----------------------------------------------------------------------------+
| Bug #: 919 Product: XalanJ2 |
! | Status: NEW Version: 2.0.0 |
! | Resolution: Platform: PC |
| Severity: Normal OS/Version: All |
| Priority: High Component: org.apache.xalan.templa |
+----------------------------------------------------------------------------+
--- 2,9 ----
| Double Check Locking scheme will not work! |
+----------------------------------------------------------------------------+
| Bug #: 919 Product: XalanJ2 |
! | Status: RESOLVED Version: 2.0.0 |
! | Resolution: FIXED Platform: PC |
| Severity: Normal OS/Version: All |
| Priority: High Component: org.apache.xalan.templa |
+----------------------------------------------------------------------------+
***************
*** 19,21 ****
--- 19,26 ----
According to some articles I have just read. The double check locking scheme
present in OutputProperties.java ( among others probably ) will not work. See:
http://www.javaworld.com/javaworld/jw-02-2001/jw-0209-toolbox.html
+
+ ------- Additional Comments From [EMAIL PROTECTED] 2001-08-03 07:21 -------
+ From what I can tell, all instances of double-check locking are fixed. Since
+ there's no way to positivily test this, I would like to close this bug and just
+ keep an eye out in the code for this kind of thing in the future.
\ No newline at end of file
