]
Max Rydahl Andersen commented on JBIDE-5790:
--------------------------------------------
JBIDE-5524 relates to this but that were done back in december.
Sources are not available in debug mode for JBoss AS Servers
-------------------------------------------------------------
Key: JBIDE-5790
URL:
https://jira.jboss.org/jira/browse/JBIDE-5790
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.CR2
Environment: JBossTools JBossAS 2.1.0.v201001140901N-H132-CR2
Reporter: Denis Golovin
Assignee: Rob Stryker
Fix For: 3.1.0.CR2
I started in a new workspace and used a new JBoss AS 5.1 instance. I added the JBoss
-> JBoss v5.0 runtime (the ones that comes bundled with WTP) and deployed my simple
hello world test app to it. I added a break-point in a .java file that's within the
project and when it hit, I could see the source of this class as expected.
I then removed the project from the server and also manually removed the .ear file from
the JBoss AS deploy directory (the standard runtime doesn't do that unfortunately).
Then I added the JBoss Community -> JBoss AS 5.1 runtime (the one from JBoss AS tools)
and again deployed my simple hello world test app to it. Added the break point again, but
when I hit I didn't get to see the source this time. Just the default white editor
with the red "Source not found." and the single button "Edit Source Lookup
Path...".
I inspected the lauch configuration of both servers. When I have nothing deployed to the
JBoss -> Jboss v5.0 runtime, the source tab shows an entry called "Default",
which contains only the base JDK jars. However, as soon as I add (publish/deploy) my
project to the JBoss v5.0 runtime, the "Default" entry in the source tab
contains all JBoss jars and folders for both the web module and the ejb module of my test
project.
The JBoss Community -> JBoss AS 5.1 runtime however in both cases (nothing deployed to
it and my test project deployed to it) shows the same standard JDK classes under
"Default" and nothing else.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: