From hinkmond.wong at oracle.com Tue Mar 4 15:51:39 2014 From: hinkmond.wong at oracle.com (Hinkmond Wong) Date: Tue, 04 Mar 2014 15:51:39 -0800 Subject: jmx-dev New release for JSR 3, Java Management Extensions (JMX) 1.4 MR Message-ID: <5316670B.3000607@oracle.com> We are very happy to announce the latest release of JSR 3, Java Management Extensions (JMX) 1.4 Maintenance Release (MR). In this latest MR, we have included the following changes: JSR 3 1.4 MR Changes List . Thank you to everyone who has helped in the creation of this release! For the RI, see inside the JDK 8 RI: https://jdk8.java.net/java-se-8-ri/ For the TCK, refer to this link: http://openjdk.java.net/groups/conformance/JckAccess/ Best Regards, Hinkmond JSR 3, MR spec lead -- Oracle Hinkmond Wong | Consulting Member of Technical Staff Phone: _+1 408.276.7618_ | Fax: _+1 408.276.7674_ Oracle Java Embedded 4210 Network Ci., M/S USCA22-rm2364 | Santa Clara, CA 95054 Green Oracle Oracle is committed to developing practices and products that help protect the environment -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jmx-dev/attachments/20140304/905631c4/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: oralogo-small.gif Type: image/gif Size: 2059 bytes Desc: not available Url : http://mail.openjdk.java.net/pipermail/jmx-dev/attachments/20140304/905631c4/oralogo-small.gif -------------- next part -------------- A non-text attachment was scrubbed... Name: oragreen.gif Type: image/gif Size: 356 bytes Desc: not available Url : http://mail.openjdk.java.net/pipermail/jmx-dev/attachments/20140304/905631c4/oragreen.gif From hinkmond.wong at oracle.com Tue Mar 4 15:54:05 2014 From: hinkmond.wong at oracle.com (Hinkmond Wong) Date: Tue, 04 Mar 2014 15:54:05 -0800 Subject: jmx-dev New release for JSR 160, Java Management Extensions (JMX) Remote API In-Reply-To: <5316670B.3000607@oracle.com> References: <5316670B.3000607@oracle.com> Message-ID: <5316679D.6040004@oracle.com> We are very happy to announce the latest release of JSR 160, Java Management Extensions (JMX) Remote API 1.4 Maintenance Release (MR). In this latest MR, we have included the following changes: JSR 160 1.4 MR Changes List . Thank you to everyone who has helped in the creation of this release! For the RI, see inside the JDK 8 RI: https://jdk8.java.net/java-se-8-ri/ For the TCK, refer to this link: http://openjdk.java.net/groups/conformance/JckAccess/ Best Regards, Hinkmond JSR 160, MR spec lead -- Oracle Hinkmond Wong | Consulting Member of Technical Staff Phone: _+1 408.276.7618_ | Fax: _+1 408.276.7674_ Oracle Java Embedded 4210 Network Ci., M/S USCA22-rm2364 | Santa Clara, CA 95054 Green Oracle Oracle is committed to developing practices and products that help protect the environment -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jmx-dev/attachments/20140304/7390c623/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: oralogo-small.gif Type: image/gif Size: 2059 bytes Desc: not available Url : http://mail.openjdk.java.net/pipermail/jmx-dev/attachments/20140304/7390c623/oralogo-small.gif -------------- next part -------------- A non-text attachment was scrubbed... Name: oragreen.gif Type: image/gif Size: 356 bytes Desc: not available Url : http://mail.openjdk.java.net/pipermail/jmx-dev/attachments/20140304/7390c623/oragreen.gif From hinkmond.wong at oracle.com Tue Mar 4 15:56:19 2014 From: hinkmond.wong at oracle.com (Hinkmond Wong) Date: Tue, 04 Mar 2014 15:56:19 -0800 Subject: jmx-dev New release for JSR 3, Java Management Extensions (JMX) 1.4 MR In-Reply-To: <5316670B.3000607@oracle.com> References: <5316670B.3000607@oracle.com> Message-ID: <53166823.1010004@oracle.com> Additional direct link to the JSR 3, Java Management Extensions (JMX) 1.4 MR page: https://jcp.org/aboutJava/communityprocess/mrel/jsr003/index4.html On 3/4/2014 3:51 PM, Hinkmond Wong wrote: > We are very happy to announce the latest release of JSR 3, Java > Management Extensions (JMX) 1.4 Maintenance Release (MR). In this > latest MR, we have included the following changes: JSR 3 1.4 MR > Changes List > . > Thank you to everyone who has helped in the creation of this release! > > For the RI, see inside the JDK 8 RI: > https://jdk8.java.net/java-se-8-ri/ > > For the TCK, refer to this link: > http://openjdk.java.net/groups/conformance/JckAccess/ > > > Best Regards, > > Hinkmond > JSR 3, MR spec lead > > -- > Oracle > > Hinkmond Wong | Consulting Member of Technical Staff > Phone: _+1 408.276.7618_ | Fax: _+1 408.276.7674_ > Oracle Java Embedded > 4210 Network Ci., M/S USCA22-rm2364 | Santa Clara, CA 95054 > Green Oracle Oracle is committed to > developing practices and products that help protect the environment > -- Oracle Hinkmond Wong | Consulting Member of Technical Staff Phone: _+1 408.276.7618_ | Fax: _+1 408.276.7674_ Oracle Java Embedded 4210 Network Ci., M/S USCA22-rm2364 | Santa Clara, CA 95054 Green Oracle Oracle is committed to developing practices and products that help protect the environment -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jmx-dev/attachments/20140304/8f385d33/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 2059 bytes Desc: not available Url : http://mail.openjdk.java.net/pipermail/jmx-dev/attachments/20140304/8f385d33/attachment-0002.gif -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 356 bytes Desc: not available Url : http://mail.openjdk.java.net/pipermail/jmx-dev/attachments/20140304/8f385d33/attachment-0003.gif -------------- next part -------------- A non-text attachment was scrubbed... Name: oralogo-small.gif Type: image/gif Size: 2059 bytes Desc: not available Url : http://mail.openjdk.java.net/pipermail/jmx-dev/attachments/20140304/8f385d33/oralogo-small-0001.gif -------------- next part -------------- A non-text attachment was scrubbed... Name: oragreen.gif Type: image/gif Size: 356 bytes Desc: not available Url : http://mail.openjdk.java.net/pipermail/jmx-dev/attachments/20140304/8f385d33/oragreen-0001.gif From hinkmond.wong at oracle.com Tue Mar 4 15:57:00 2014 From: hinkmond.wong at oracle.com (Hinkmond Wong) Date: Tue, 04 Mar 2014 15:57:00 -0800 Subject: jmx-dev New release for JSR 160, Java Management Extensions (JMX) Remote API In-Reply-To: <5316679D.6040004@oracle.com> References: <5316670B.3000607@oracle.com> <5316679D.6040004@oracle.com> Message-ID: <5316684C.40402@oracle.com> Additional direct link to the JSR 160, Java Management Extensions (JMX) Remote API 1.4 MR page: https://jcp.org/aboutJava/communityprocess/mrel/jsr160/index2.html On 3/4/2014 3:54 PM, Hinkmond Wong wrote: > We are very happy to announce the latest release of JSR 160, Java > Management Extensions (JMX) Remote API 1.4 Maintenance Release (MR). > In this latest MR, we have included the following changes: JSR 160 1.4 > MR Changes List > . > Thank you to everyone who has helped in the creation of this release! > > For the RI, see inside the JDK 8 RI: > https://jdk8.java.net/java-se-8-ri/ > > For the TCK, refer to this link: > http://openjdk.java.net/groups/conformance/JckAccess/ > > > Best Regards, > > Hinkmond > JSR 160, MR spec lead > > -- > Oracle > > Hinkmond Wong | Consulting Member of Technical Staff > Phone: _+1 408.276.7618_ | Fax: _+1 408.276.7674_ > Oracle Java Embedded > 4210 Network Ci., M/S USCA22-rm2364 | Santa Clara, CA 95054 > Green Oracle Oracle is committed to > developing practices and products that help protect the environment > -- Oracle Hinkmond Wong | Consulting Member of Technical Staff Phone: _+1 408.276.7618_ | Fax: _+1 408.276.7674_ Oracle Java Embedded 4210 Network Ci., M/S USCA22-rm2364 | Santa Clara, CA 95054 Green Oracle Oracle is committed to developing practices and products that help protect the environment -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jmx-dev/attachments/20140304/67e23b51/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 2059 bytes Desc: not available Url : http://mail.openjdk.java.net/pipermail/jmx-dev/attachments/20140304/67e23b51/attachment.gif -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 356 bytes Desc: not available Url : http://mail.openjdk.java.net/pipermail/jmx-dev/attachments/20140304/67e23b51/attachment-0001.gif -------------- next part -------------- A non-text attachment was scrubbed... Name: oralogo-small.gif Type: image/gif Size: 2059 bytes Desc: not available Url : http://mail.openjdk.java.net/pipermail/jmx-dev/attachments/20140304/67e23b51/oralogo-small.gif -------------- next part -------------- A non-text attachment was scrubbed... Name: oragreen.gif Type: image/gif Size: 356 bytes Desc: not available Url : http://mail.openjdk.java.net/pipermail/jmx-dev/attachments/20140304/67e23b51/oragreen.gif From Alan.Bateman at oracle.com Tue Mar 25 19:04:49 2014 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Tue, 25 Mar 2014 19:04:49 +0000 Subject: jmx-dev 8038343: Eliminate use of reflection to access JavaBeans Introspector Message-ID: <5331D351.4070701@oracle.com> Currently the introspection code in the JMX monitor API uses core reflection to access the JavaBeans Introspector. This came about when we had to eliminate this dependency - for example in the subset Profiles of Java SE then compact3 defines the JMX API but doesn't have java.beans. I'd like to clean this up further and replace the reflection hack with a solution that uses the SharedSecrets mechanism. The reason is to avoid needing to suppress the access check when we move to modules in the future. The webrev with the proposed changes is here: http://cr.openjdk.java.net/~alanb/8038343/webrev/ The changes are very simple and the only non-obvious thing is that the JMX introspector needs to ensure that the beans Introspector is initialized so this is the reason for the Class.forName. I've tried a number of other approaches to this but this one seems to simplest. Thanks, Alan. From fw at deneb.enyo.de Tue Mar 25 19:29:36 2014 From: fw at deneb.enyo.de (Florian Weimer) Date: Tue, 25 Mar 2014 20:29:36 +0100 Subject: jmx-dev 8038343: Eliminate use of reflection to access JavaBeans Introspector In-Reply-To: <5331D351.4070701@oracle.com> (Alan Bateman's message of "Tue, 25 Mar 2014 19:04:49 +0000") References: <5331D351.4070701@oracle.com> Message-ID: <87k3bi13hb.fsf@mid.deneb.enyo.de> * Alan Bateman: > I'd like to clean this up further and replace the reflection hack with > a solution that uses the SharedSecrets mechanism. The reason is to > avoid needing to suppress the access check when we move to modules in > the future. The webrev with the proposed changes is here: > > http://cr.openjdk.java.net/~alanb/8038343/webrev/ Could you use a lambda expression in Introspector? From mandy.chung at oracle.com Tue Mar 25 20:15:15 2014 From: mandy.chung at oracle.com (Mandy Chung) Date: Tue, 25 Mar 2014 13:15:15 -0700 Subject: jmx-dev 8038343: Eliminate use of reflection to access JavaBeans Introspector In-Reply-To: <5331D351.4070701@oracle.com> References: <5331D351.4070701@oracle.com> Message-ID: <5331E3D3.1050902@oracle.com> On 3/25/2014 12:04 PM, Alan Bateman wrote: > > Currently the introspection code in the JMX monitor API uses core > reflection to access the JavaBeans Introspector. This came about when > we had to eliminate this dependency - for example in the subset > Profiles of Java SE then compact3 defines the JMX API but doesn't have > java.beans. > > I'd like to clean this up further and replace the reflection hack with > a solution that uses the SharedSecrets mechanism. The reason is to > avoid needing to suppress the access check when we move to modules in > the future. The webrev with the proposed changes is here: > > http://cr.openjdk.java.net/~alanb/8038343/webrev/ > > The changes are very simple and the only non-obvious thing is that the > JMX introspector needs to ensure that the beans Introspector is > initialized so this is the reason for the Class.forName. I've tried a > number of other approaches to this but this one seems to simplest. This looks good. Using the SharedSecrets mechanism is a better solution. I generally prefer to use the 3-arg Class.forName to explicitly pass the class loader but it's really minor. Mandy From Alan.Bateman at oracle.com Tue Mar 25 20:28:25 2014 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Tue, 25 Mar 2014 20:28:25 +0000 Subject: jmx-dev 8038343: Eliminate use of reflection to access JavaBeans Introspector In-Reply-To: <5331E3D3.1050902@oracle.com> References: <5331D351.4070701@oracle.com> <5331E3D3.1050902@oracle.com> Message-ID: <5331E6E9.6040604@oracle.com> On 25/03/2014 20:15, Mandy Chung wrote: > > This looks good. Using the SharedSecrets mechanism is a better > solution. I generally prefer to use the 3-arg Class.forName to > explicitly pass the class loader but it's really minor. That's a good point, it is more obvious when using the 3-arg method. I'll change it before pushing - thanks! -Alan From Alan.Bateman at oracle.com Tue Mar 25 20:29:49 2014 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Tue, 25 Mar 2014 20:29:49 +0000 Subject: jmx-dev 8038343: Eliminate use of reflection to access JavaBeans Introspector In-Reply-To: <87k3bi13hb.fsf@mid.deneb.enyo.de> References: <5331D351.4070701@oracle.com> <87k3bi13hb.fsf@mid.deneb.enyo.de> Message-ID: <5331E73D.8080700@oracle.com> On 25/03/2014 19:29, Florian Weimer wrote: > * Alan Bateman: > >> : >> >> http://cr.openjdk.java.net/~alanb/8038343/webrev/ > Could you use a lambda expression in Introspector? Which of the Introspectors do you see the opportunity, my IDE didn't spot any. -Alan From fw at deneb.enyo.de Tue Mar 25 20:33:45 2014 From: fw at deneb.enyo.de (Florian Weimer) Date: Tue, 25 Mar 2014 21:33:45 +0100 Subject: jmx-dev 8038343: Eliminate use of reflection to access JavaBeans Introspector In-Reply-To: <5331E73D.8080700@oracle.com> (Alan Bateman's message of "Tue, 25 Mar 2014 20:29:49 +0000") References: <5331D351.4070701@oracle.com> <87k3bi13hb.fsf@mid.deneb.enyo.de> <5331E73D.8080700@oracle.com> Message-ID: <87pplayq52.fsf@mid.deneb.enyo.de> * Alan Bateman: >>> http://cr.openjdk.java.net/~alanb/8038343/webrev/ >> Could you use a lambda expression in Introspector? > Which of the Introspectors do you see the opportunity, my IDE didn't > spot any. Oh, there are two. I meant the inner class in java.beans.Introspector. From Alan.Bateman at oracle.com Tue Mar 25 20:46:00 2014 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Tue, 25 Mar 2014 20:46:00 +0000 Subject: jmx-dev 8038343: Eliminate use of reflection to access JavaBeans Introspector In-Reply-To: <87pplayq52.fsf@mid.deneb.enyo.de> References: <5331D351.4070701@oracle.com> <87k3bi13hb.fsf@mid.deneb.enyo.de> <5331E73D.8080700@oracle.com> <87pplayq52.fsf@mid.deneb.enyo.de> Message-ID: <5331EB08.7060402@oracle.com> On 25/03/2014 20:33, Florian Weimer wrote: > * Alan Bateman: > >>>> http://cr.openjdk.java.net/~alanb/8038343/webrev/ >>> Could you use a lambda expression in Introspector? >> Which of the Introspectors do you see the opportunity, my IDE didn't >> spot any. > Oh, there are two. I meant the inner class in java.beans.Introspector. Thanks, done, one less inner class. -Alan. From sergey.malenkov at oracle.com Wed Mar 26 12:17:24 2014 From: sergey.malenkov at oracle.com (sergey malenkov) Date: Wed, 26 Mar 2014 16:17:24 +0400 Subject: jmx-dev 8038343: Eliminate use of reflection to access JavaBeans Introspector In-Reply-To: <5331D351.4070701@oracle.com> References: <5331D351.4070701@oracle.com> Message-ID: <5332C554.1000905@oracle.com> The fix looks good to me. Thanks, SAM On 25.03.2014 23:04, Alan Bateman wrote: > > Currently the introspection code in the JMX monitor API uses core > reflection to access the JavaBeans Introspector. This came about when > we had to eliminate this dependency - for example in the subset > Profiles of Java SE then compact3 defines the JMX API but doesn't have > java.beans. > > I'd like to clean this up further and replace the reflection hack with > a solution that uses the SharedSecrets mechanism. The reason is to > avoid needing to suppress the access check when we move to modules in > the future. The webrev with the proposed changes is here: > > http://cr.openjdk.java.net/~alanb/8038343/webrev/ > > The changes are very simple and the only non-obvious thing is that the > JMX introspector needs to ensure that the beans Introspector is > initialized so this is the reason for the Class.forName. I've tried a > number of other approaches to this but this one seems to simplest. > > Thanks, > > Alan.