- This topic has 3 replies, 2 voices, and was last updated 16 years, 9 months ago by
.
-
Posts
-
I’m trying to debug a custom (ice)faces component and needed to see Sun’s jsf-ri source. I realized that my eclipse project was linking to the MyEclipse library Java EE 5, which contains javaee.jar, jsf-api.jar, jsf-ri.jar, yet my app runs in jboss 4.2.1 which contains it’s own jsf jars (not necessarily different, but I want to be sure I’m linking the right source with the right jars.) So I removed Java EE 5 from the build path and created a user library that contains references to the jsf jars from jboss.
That part went fine. Now I’m debugging my app but I can’t get to the jsf sources I linked to those jars. When I try to step into UIComponentBase.encodeBegin I get the “no source attachment” page, which is looking in javaee.jar! However if I manually walk through the code and ctrl+click on UIComponent.encodeBegin the source appears as it should.
I guess I should clarify a little…when I ctrl+click on the method I want to step into I’m taken to the reference of the interface UIComponent, which is implemented in UIComponentBase, the class the debugger is trying to find. So maybe there’s a discrepancy there, but both of those are implemented in jsf-api.jar so you’d think if it finds one it finds both.
A little more testing revealed that if I navigate to UIComponentBase.class (in jsf-api.jar that I’ve linked to in my user lib) through the package explorer and set a break point the app will break as expected, but still shows the source attachment not found page for javaee.jar.
