[ 
https://issues.apache.org/jira/browse/WICKET-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Martin Grigorov resolved WICKET-4324.
-------------------------------------

    Resolution: Cannot Reproduce

I just added package private methods locally to
org.apache.wicket.proxy.util.InterfaceObject
and
org.apache.wicket.proxy.util.ConcreteObject

and this didn't break org.apache.wicket.proxy.LazyInitProxyFactoryTest.

Please modify this test so that it breaks and attach the patch here. We will 
reopen the ticket. 
                
> [wicket-ioc] LazyInitProxyFactory CGLIB proxies naming strategy may cause 
> java.lang.IllegalAccessError
> ------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-4324
>                 URL: https://issues.apache.org/jira/browse/WICKET-4324
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-spring
>            Reporter: S Mathez
>              Labels: proxy
>
> A CGLib proxy created by LazyInitProxyFactory may cause 
> java.lang.IllegalAccessError when the target class has "package-private" 
> method.
> I think the root cause of this problem is the choosen strategy for naming 
> proxies (see WICKET-1162) : after adding "WICKET_" before the package name of 
> the target class, the proxy becomes a member of a new package. (This 
> behaviour is different as which is used by CGLib DefaultNamingPolicy).
> Why not adding "_WICKET" *after* the name of the target class ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to