You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2017/06/19 19:42:00 UTC

[jira] [Assigned] (WICKET-4324) [wicket-ioc] LazyInitProxyFactory CGLIB proxies naming strategy may cause java.lang.IllegalAccessError

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

Martin Grigorov reassigned WICKET-4324:
---------------------------------------

    Assignee: Martin Grigorov

> [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
>            Assignee: Martin Grigorov
>              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 was sent by Atlassian JIRA
(v6.4.14#64029)