Re: Source Path not working

As with all of the sourcepath related questions, I can be of no use 
without detailed examples of what you tried to do. In particular, I 
would need to see:

1. The full path of a .java file.

2. The sourcepath setting in JSwat.

3. The output from the 'source' command for the class that is defined in 
the .java file from #1 above.

When you say JSwat failed to install on Windows, what do you mean? What 
was the reason for the failure?

If you connected JSwat to the debuggee and there are no classes showing 
in the Classes panel, then it did not really connect. There is 
absolutely no way for the Classes panel to be empty if the debuggee is 
properly connected (some classes are loaded even when you suspend the 
debuggee on startup).

n


Roger Mori-Tuesta wrote:
> Dear Partners:
> 
> I'm trying to use jswat to debug a huge production
> application running JDK 1.4.x, Tomcat 4.1 over Red Hat EL.
> 
> The application is installed at the same directory level as webapp
> (*.jsp,, *.tld) in the tomcat_home directory. Also, this application 
> contains all the
> *.java and *.class files  in the WEB-INF/classes directory.
> 
> The source files are located in a heterogeneous directory structure 
> managed by
> Microsoft Source Safe (CVS) software.
> 
> I failed installing latest version of jswat on a windows machine running 
> jdk 1.5.8
> Attaches de JVM  (jdk 1.4 red ) but  after oppening a browser no classes 
> show up in
> the classes pane.
> 
> I downloaded JSwat 2.39 and intalled in the Red Hat server computer 
> getting the same problem.
> The connection works but this message appears: "The source for the class 
> org.apache.jsp.jsp2.el.functions_jsp could not be found. In the future, 
> this view will show the class byte code".
> 
> I have tryed everything following the documentation and email of this 
> list; Even I have created
> links to simulate the path org.apache.jsp and used the "source 
> class-name command" along with the source path in all its flavors.
> 
> Please, advice.
> 
> Thank you.
> 
> Roger.
> [email protected]