File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes EJB and other Java EE Technologies and the fly likes Debugging / Source Code Availability Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Soft Skills this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Debugging / Source Code Availability" Watch "Debugging / Source Code Availability" New topic
Author

Debugging / Source Code Availability

M Kilby
Greenhorn

Joined: Jul 30, 2008
Posts: 7
Hi - we're developing web apps and have a number of binaries (JARs) which get incuded, the apps ulimately deploy to IBM's WAS.

We develop the web part against Tomcat - it's much quicker.

Within Tomcat we can debug our code within the JARs (we include the source when we build the JARs).

However when we package the web app up into an EAR file (for deployment to WAS) and try to debug on the WAS platform - the debugger is unable to locate the source code for the lines of code within the JARs.

This is most frustrating.

We only switched to using JARs recently - prior to this we had project open in our workspace and debugging in this context wasn't an issue for locating source code.

Any help is appreciated.

Regards,
Mark.
Reza Rahman
author
Ranch Hand

Joined: Feb 01, 2005
Posts: 580
    
    5
Mark,

What version of WAS are you using? You should be able to do this if you make sure the IDE is turning on remote debugging properly (Tomcat does the same thing)? I know for sure that JBoss, GlassFish and WebLogic supports this, but I'm not sure about WAS. If it helps, here are the instructions for WebLogic: http://www.oracle.com/technology/products/jdev/howtos/weblogic/remotedebugwls.html.

Best regards,
Reza


Independent Consultant — Author, EJB 3 in Action — Expert Group Member, Java EE 6 and EJB 3.1
M Kilby
Greenhorn

Joined: Jul 30, 2008
Posts: 7
Hi Reza,

We're running WAS 6.1.

I looked through the WebLogic doc and couldn't see anything. I also checked our projects and server properties for any debug config options - couldn't see any that might help.

The source is included in the JARs.

After we have started the server in debug mode and RC one of the JSP files to kick things off, we can actually debug no problem up to the point where (for example) the faces beans make a call to one of the JARs. We lose visibility until the thread returns to the caller.

This particular problem applies to our local development workstations where WAS is running locally.


Regards,
Mark.
Reza Rahman
author
Ranch Hand

Joined: Feb 01, 2005
Posts: 580
    
    5
Mark,

Looks like it is time to utilize those over-priced IBM support licenses :-).

Cheers,
Reza
M Kilby
Greenhorn

Joined: Jul 30, 2008
Posts: 7
Reza,

You may be right.

At the moment we work-around this by reverting to our old model which is to include projects in the workspace in exploded form - so to speak.

I've put in a reminder to come back to this thread and provide the solution IBM give.

Regards and thanks for your help.
Mark.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Debugging / Source Code Availability