Le 26 mars 2010 à 21:37, [email protected] a écrit : > Still posting on the very same problem... > > While trying to close the gap between some working pet examples, > and the complete failing application, I come up with the following code > samples. The first one works perfectly, while the second one raises the > infamous "java.dyn.NoAccessException" that is beginning to cause me > a slight headache... > > The only difference between the code samples is that the failing one > tries to use a method handle whose signature contains a user-defined > class. In particular, it should be noted that access qualifiers are strictly > the same in both code samples. Just in case someone is wondering, > making the "p.Param" class public do not solve the problem.
(...) As stated in the title, here is a (hopefully temporary) workaround for my problem: just add the classes to the bootclasspath by using the "-Xbootclasspath/p" command-line switch. However, I am still interested my any insight about the problem. Xavier Clerc -- You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en.
