[
https://issues.apache.org/jira/browse/WICKET-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16054653#comment-16054653
]
ASF subversion and git services commented on WICKET-4324:
---------------------------------------------------------
Commit 27b9a67d9e986d8998888e9984125ce2a2248498 in wicket's branch
refs/heads/wicket-7.x from [~mgrigorov]
[ https://git-wip-us.apache.org/repos/asf?p=wicket.git;h=27b9a67 ]
WICKET-4324 [wicket-ioc] LazyInitProxyFactory CGLIB proxies naming strategy may
cause java.lang.IllegalAccessError
Change the calculation of the 'prefix' in WicketNamingStrategy from
'WICKET_package.Class' to 'package.Wicket_Proxy_Class'
> [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)
