You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Brent L Johnson <br...@bjohnson.net> on 2001/10/16 16:40:02 UTC
parseInt() Java code errors
I've got a development machine and a production machine, both running Cocoon
1.8 under Tomcat on a Unix machine.
I've made changes to my development environment and added a new logicsheet
that will generate the header for the pages. I added the logicsheet to all
my xml documents, and they worked FINE in development.
When I pushed these changes into production, I started getting parseInt()
errors in the Java code thats being generated by Cocoon/Tomcat (it only
seems to be on pages that use other logicsheets, and make esql calls). I
checked the actual Java code, and the error is in the internal ESQL code.
It has to do with a parseInt() on the "max_rows" of the esql statement -
which in the case of my generated code is "" (which generates a parseInt()
exception). Also, let me reiterate, this parseInt() is NOT in my
logicsheet - it's generated by Cocoon.
Could someone please tell me how esql and/or Cocoon is generating a
parseInt() exception in production and not development? (these are the
EXACT same files - I use RSYNC to sync up all the files). And why it would
generate a parseInt() exception in the code generated by Cocoon/Tomcat??
I've temporarily fixed this by removing the logicsheet from the affected
pages, and relying on a static stylesheet template tag to create a
non-dynamic header.
Thanks,
- Brent
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: parseInt() Java code errors
Posted by Brent L Johnson <br...@bjohnson.net>.
Here's another little update....
I downloaded the compiled java file from the production repository, and I
compared that to the compiled java code in development.
The 2 files are exactly the same other than some esql Exception type codes
in the catch statements (which looked to be generated names - so that
shouldnt cause anything like this). Can anyone think of what could be
causing this???
I even took the esql parseInt() try/catch section of code in the compiled
java file and copied that by itself and executed it. It was fine - not
throwing any sort of NumberFormatException. Is there a way I could find out
exactly WHERE this NumberFormatException was occuring? Apparenly it's in
some object call or something that's not in the generated code.
Thanks,
- Brent
----- Original Message -----
From: "Brent L Johnson" <br...@bjohnson.net>
To: "Cocoon-Users" <co...@xml.apache.org>
Sent: Tuesday, October 16, 2001 10:40 AM
Subject: parseInt() Java code errors
> I've got a development machine and a production machine, both running
Cocoon
> 1.8 under Tomcat on a Unix machine.
> I've made changes to my development environment and added a new logicsheet
> that will generate the header for the pages. I added the logicsheet to
all
> my xml documents, and they worked FINE in development.
>
> When I pushed these changes into production, I started getting parseInt()
> errors in the Java code thats being generated by Cocoon/Tomcat (it only
> seems to be on pages that use other logicsheets, and make esql calls). I
> checked the actual Java code, and the error is in the internal ESQL code.
> It has to do with a parseInt() on the "max_rows" of the esql statement -
> which in the case of my generated code is "" (which generates a parseInt()
> exception). Also, let me reiterate, this parseInt() is NOT in my
> logicsheet - it's generated by Cocoon.
>
> Could someone please tell me how esql and/or Cocoon is generating a
> parseInt() exception in production and not development? (these are the
> EXACT same files - I use RSYNC to sync up all the files). And why it
would
> generate a parseInt() exception in the code generated by Cocoon/Tomcat??
>
> I've temporarily fixed this by removing the logicsheet from the affected
> pages, and relying on a static stylesheet template tag to create a
> non-dynamic header.
>
> Thanks,
>
> - Brent
>
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>
> To unsubscribe, e-mail: <co...@xml.apache.org>
> For additional commands, e-mail: <co...@xml.apache.org>
>
>
>
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>