Dear Jochen, >this means you want the Groovy program to access the private method a >Java class, right?
Yes, I intend that. >Does MagicAccessorImpl prevent access checks? It does prevent bytecode >verification, which allows us to load the generated class faster. Yes, according to the javadoc of MagicAccessorImpl it prevents access checking and bytecode verification. >But I don't think that this access check falls under the magic as well. >Groovy should have accessed by reflection only instead in non-indy mode. At first I thought so too, but it seems that Groovy calls the private method directly. I think that some direct calling byte-code is generated by CallSiteGenerator.compilePojoMethod() in CachedMethod.createPojoMetaMethodSite(). >Could you please tell us the version of Groovy you are using as well? I'm using Groovy 3.0.3 with Windows 10. Regards, Tomokazu Harada ***************************************************************** This e-mail and any attachments are intended only for the named addressee(s) and may contain confidential information. If you have received this e-mail in error, please delete the e-mail and any attachments and notify the sender immediately. If you are not the intended recipient, any disclosure, copying, printing, transmission or distribution of, or any action taken in reliance upon, the information contained in this e-mail and any attachments is strictly prohibited. このメール及び添付資料には機密情報を含む場合があります。 本メールにお心当たりのない場合は、速やかに破棄頂くとともに、 送信元へその旨ご連絡ください。また、本メール及び添付資料に ついては、一切の開示、複写、配布、その他の利用、または、 記載内容に基づくいかなる行動もされないようにお願いします。 *****************************************************************
