From Stanley.Ho at sun.com Thu May 1 13:48:11 2008 From: Stanley.Ho at sun.com (Stanley M. Ho) Date: Thu, 01 May 2008 13:48:11 -0700 Subject: JavaOne Message-ID: <481A2C8B.3010807@sun.com> Hi JSR 277 experts, Here is the schedule for JSR 277 and related talks by EG members at JavaOne next week: * TS-6185: Modularity in Java? Platform Wednesday 5/7/2008 10:50 AM -11:50 AM * BOF-5032: Modularity in the Java? Platform Wednesday 5/7/2008 8:30 PM -9:20 PM * BOF-6180: Class Loader Rearchitected Wednesday 5/7/2008 7:30 PM -8:20 PM * TS-5122 Converting (Large) Applications to OSGi BJ Hargrave, IBM; Peter Kriens, aQute Thursday 5/8/2008 13:30 - 14:30 We know some of you will be at the conference, and we hope to meet you at the modularity session and BOF! - Stanley and Alex From andyp at bea.com Tue May 6 11:07:27 2008 From: andyp at bea.com (Andy Piper) Date: Tue, 06 May 2008 19:07:27 +0100 Subject: Classloading synchronization & 277 In-Reply-To: <48121BA2.7060001@oracle.com> References: <47F46ABF.1020306@sun.com> <48121BA2.7060001@oracle.com> Message-ID: <6.2.5.6.2.20080506190311.05196010@bea.com> Hi Stanley Apologies if this has been brought up before, I know that Glyn raised something similar a long time ago. http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4670071 is scheduled to be fixed in Dolphin. Is this on the radar of your development team? How are you planning to integrate this into 277? Current OSGi implementations really need this bug fixed in order to be able to support cycles without deadlocks. I expect that any interoperation with OSGi would also mean that 277 would be reliant on this also. Thanks andy Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. From Stanley.Ho at sun.com Thu May 15 11:44:48 2008 From: Stanley.Ho at sun.com (Stanley M. Ho) Date: Thu, 15 May 2008 11:44:48 -0700 Subject: Classloading synchronization & 277 In-Reply-To: <6.2.5.6.2.20080506190311.05196010@bea.com> References: <47F46ABF.1020306@sun.com> <48121BA2.7060001@oracle.com> <6.2.5.6.2.20080506190311.05196010@bea.com> Message-ID: <482C84A0.70307@sun.com> Hi Andy, Yes, this issue is on the radar of our classloader re-achitecture team (Karen Kinner and Iris Clark are the leads). The current proposed solution would require a custom classloader implementation to implement a few new methods in order to enable parallel classloading to workaround this issue. In 277, I expect the spec will require the classloaders in the module system implementations to support parallel classloading. If an OSGi container implements the 277 abstractions, the classloaders it exposes through the abstractions must also support parallel classloading. - Stanley Andy Piper wrote: > Hi Stanley > > Apologies if this has been brought up before, I know that Glyn raised > something similar a long time ago. > > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4670071 > > is scheduled to be fixed in Dolphin. Is this on the radar of your > development team? How are you planning to integrate this into 277? > > Current OSGi implementations really need this bug fixed in order to > be able to support cycles without deadlocks. I expect that any > interoperation with OSGi would also mean that 277 would be reliant on > this also. > > Thanks > > andy > > > > Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.