I'm surprised there still a problem, we really hit all the available cases. It's tricky to do it right.
In any case, 5.2.2 has a JVM system property that turns of the live service reloading logic (it doesn't affect reloading of components). 2010/10/14 Vjeran Marcinko <vjeran.marci...@email.t-com.hr>: > Hi. > > Similar as in version 5.2.0, and now in 5.2.1, my custom service > (ComponentRequestHandler) registered in my module class still throws > IllegalAccessError as in 5.2.0 since it accesses package-private static > method in utility helper class. > The utility class is stateful, and later used in other parts of application. > > Is there some way to turn off this class loading behaviour altogether (i > don't care about reloading feature anyway, just want to be allowed to code > normally without having to think about class loading issues)? > > Regards, > Vjeran > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
