Not exactly JavaBeans, but pretty close... If anybody knows a better
resource on usenet for just JSP, please feel free to let me know.

Another day, another stupid question proving how little I know about
this language that I'm supposed to be coding in right now...

I have a 'subroutine' in the jsp that I'm currently working on that
works with about 20-30 different variables; general manipulation,
tossing them in to various database tables, etc... Anyway, there's a
whole load of SQL queries, inserts, and updates going on in this piece
of code, too. One of them (at least) is broken. Judging by the error
that I'm getting from the tomcat logfiles, it's in one of the queries,
and it seems that one of my variables is being interpolated as a table
column... So I need to find a way to view the SQL interactions as
they're happening or an easy way to dump all of my variables somewhere
so that I can take a peek at them in order to locate what is going on.

Commenting out all of the SQL and adding debugging output is an
option, but one that is going to be a real pain in the buttocks. I'd
much rather find an easier way.

Any ideas?

TIA

Damon Getsman wrote:

comp.lang.java.programmer might be more appropriate for pure JSP issues,
but this is really about mySql

More information in this post... Looks like the MySQL bit was fooling
me; that's a nonfatal error that likely has been there since before I
modified anything in this code.

Is there anything in this snippet of error log that can help me locate
my error? Like what line # in timesheet.jsp or index.jsp it's dying
on here? Or maybe even something subtle that I'm missing like follow
around one of the myBean.intBean objects to locate the error in one of
these files?

I really dislike the way tomcat reports errors.

-Damon

PS I am posting this new information to the newsgroup you recommended
as well if it is, indeed, more appropriate there.

Sep 17, 2008 1:49:02 PM org.apache.catalina.core.ApplicationDispatcher
invoke
SEVERE: Servlet.service() for servlet jsp threw exception
java.lang.NumberFormatException: null
at java.lang.Integer.parseInt...

I just posted what I hope is some helpful tips over on
comp.lang.java.programmer.

Damon Getsman wrote:

...