It's not that it doesn't allow reflection. It's not allowing you to bypass the Java language access restrictions by calling AccessibleObject.setAccessible(true). That's not necessarily a bad thing have. When turned off, it allows outside classes to write to private fields in your code! Of course, that's the whole idea behind the dependency injection support (@SpringBean) in Wicket.
On May 11, 2009 8:47 AM, "Brill Pappin" <[email protected]> wrote: Looks to me as if the jvm you are deploying to has an active security policy that doesn't allow reflection... Which is going to make most java apicatipns fail because it's such a common method of doing things. If you have control of the system, check the policy files (it could also be a bad java install ok the box, although I've never seen one fail like that). - Brill Pappin Sent from my mobile. On 11-May-09, at 4:24 AM, Anders Peterson <[email protected]> wrote: > What exactly does this ...
