Have proxies generated by ByteBuddy to conform to legacy naming strategies

Description

We should take in consideration the suggestion at https://jira.spring.io/browse/SPR-16569?focusedCommentId=157776&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-157776

Essentially it seems that proxies being generated now by Byte Buddy can't be recognized by Spring as proxies, as they used to look for "$$" in the generated classnames.

Would be great to be able to restore the naming convention, at least for the foreseable future. I'm not sure if we should commit on that naming strategy for the long term, let's talk about that.

My primary concern for the long term is that this would disable "short string representation" for the class metadata in the JVM; I realize this might sound far fetched as there's a lot more fat that should be cut first, but since we're aggressively trimming in such areas, such names being compact might become a priority too.

Activity

Show:
Fixed

Details

Assignee

Reporter

Components

Fix versions

Priority

Created March 13, 2018 at 10:56 AM
Updated April 27, 2018 at 1:37 PM
Resolved April 18, 2018 at 1:14 PM
Loading...