🚀 go-pugleaf

I found the problem, but not anywhere you suggested.  It was in the Web Application Developer's Guide: JavaServer Pages (JSP)
---------------------------------
Important: Tomcat 4.1 and Jetty (used by JBoss) do not support JSP source debugging, as both use Jasper. You can remedy this problem with the following steps: Browse to the <jbuilder>/thirdparty/jakarta-tomcat-4.0.6-LE-jdk14/lib directory.For Tomcat, copy jasper-compiler.jar and jasper-runtime.jar to the <jbuilder>/thirdparty/jakarta-tomcat-4.1.27-LE-jdk14/common/lib directory.For Jetty, search for the jasper-compiler.jar and the jasper-runtime.jar in your JBoss installation and replace them with the jasper-compiler.jar and the jasper-runtime.jar found in the <jbuilder>/thirdparty/jakarta-tomcat-4.1.0.6-LE-jdk14/common/lib directory
---------------------------------

I still cannot figure out why it stopped working last Wednesday afternoon, after I had been using it since December.

Jim McMaster
mailto:jim.mcmaster@comcast.net

"Lata Amujuri" <lamujuri@borland.com> wrote:
>Please look at Help|Help Topics. Developing Enterprise Applications. Using
>JBuilder with Tomcat. Debugging JSPs with Tomcat 4.1.
>"Jim McMaster" <jim.mcmaster@comcast.net> wrote in message
>news:404ce587$1@newsgroups.borland.com...
>>
>> I am having problems in debugging JSPs with JBX.  It worked last
>> week, now it does not.  I am on Windows, using the tomcat-4.1.27-le
>> shipped with JBX.
>>
>> Sometimes, it ignores the breakpoint completely.  Other times, it
>> stops, and says "Unable to find ConfigList_jsp in project source
>> path".  That makes some sense, sinct that file does not exist.  I
>> just wonder why it no longer is looking for the
>> ConfigList_0002ejsp_jsp it used to find.
>>
>> Any ideas?  I figure no one at TeamBozo cares about bugs, but
>> perhaps another unfortunate soul has figures out how to fix
>> this without Borland "support".
>> --
>> Jim McMaster
>> mailto: jim.mcmaster@comcast.net
>
>