]
Martin Malina closed JBIDE-20804.
---------------------------------
So despite the other bug that I found (JBIDE-20845) I was eventually able to confirm this
fix and see the source of the class that previously couldn't be loaded. (With the help
of Vlado and Rasto.) Verified in JBDS 9.0.0.CR2 B116.
Flaky source lookup while debugging apps deployed on Wildfly
------------------------------------------------------------
Key: JBIDE-20804
URL:
https://issues.jboss.org/browse/JBIDE-20804
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Affects Versions: 4.3.0.CR1
Reporter: Fred Bricon
Assignee: Fred Bricon
Priority: Critical
Fix For: 4.3.0.CR2
When debugging an application deployed on Wildfly, some sources can not be found even
though a matching source jar exists in Maven Central.
- create an html5 app
- put a breakpoint on MemberService.listAllMembers()
- Debug As > Debug on Server (choose Wildfly 10)
- when the web page is displayed, the breakpoint is hit
- go down the stacktrace, source should be downloaded for each line
- reach io.undertow.server.handlers.PredicateHandler, no source can be found
The problem is caused by the class file being found in the wildfly-cli client jar. But it
has no matching source jar containing the Predicate.java file. The same class exists in
undertow-core.jar, which has a matching source jar. But the source lookup stopped once it
found wildfly-cli.jar, regardless if an actual source could be found. It should keep
looking until an actual source is found