Hi Howard et al, We are using Tapestry 5 IoC in all our applications (both standalone and web), and have a very sizeable IoC code base. We have tried a couple of times now to upgrade it from 5.1 and 5.2.4, but it seems backwards compatibility is broken... The problem we are stuck on now is whenever a non-public method is called from within a service we are getting the dreaded IllegalAccessError. I have not dug very deep into Tapestrys internals to figure out why this is happening yet, but I am certain that in Tapestry 5.1 this is not the case.
You might suggest to simply change the scope of these methods and classes but we can't easily re-factor our library modules because of the sheer scale, and even if it were an option, and we did consider it for a time, these errors produce runtime exceptions, which makes it is very difficult to find every occurrence in the code, so for us to change the scope for our entire IoC codebase is not a practical solution. This seems like a big change from 5.1, and is a real blocker for us, I would greatly appreciate any assistance. Thanks, Peter --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
