Bug 377663 - step filtering for debugging should allow filtering generated classes like *$$...ByCGLIB$$*
Summary: step filtering for debugging should allow filtering generated classes like *$...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.8   Edit
Hardware: All All
: P3 enhancement with 7 votes (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2012-04-25 12:22 EDT by Hans-Peter Störr CLA
Modified: 2014-08-28 00:56 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hans-Peter Störr CLA 2012-04-25 12:22:24 EDT
Build Identifier: SpringSource Tool Suite   Version: 2.9.1.RELEASE Build Id: 201203221000

If you use aspects or spring proxies created by cglib you often get generated classes like SomeService$$FastClassByCGLIB$$34da776 . When stepping into a class that is wrapped by a proxy you have to step through these classes which have no source and no interesting function. Unfortunately it seems impossible to create a step filter that matches such classes. Something like *$$*, *$$FastClassByCGLIB$$*, *CGLIB* or *CGLIB$$* should work here.

Reproducible: Always

Steps to Reproduce:
Wrap a scoped spring bean into an aop-proxy and step into a method call into that bean. A bean definition would be for example:
<bean class="foo" scope="session">
  <aop:scoped-proxy/>
</bean>