At 12:19 PM -0700 7/5/00, Tom Wnuk wrote:
I was just getting a similar error but it was due to an existing jsp page that was using a tag incorrectly. In my case they we're using <%@ some java code %> which Orion didn't like and it threw an out-of-bounds exception on a String.
There's probably an JSP syntax error somewhere in your code.
Note to Orion developers:
One thing that would be more helpful, trace messages in the console window or even to a log file. Sometimes you'll get an error w/o a stack trace and all you get is an 'unable to display the page' message, not very helpful. How about msgs upon startup so we can determine what's been loaded or not, etc..
Does anyone know if tracing exists in Orion and if so, how do you turn it on?
Tom
Tom, I don't know how to turn on additional logging, but I do
know how to get better error messages: Turn off pretty error pages in
IE. On the Tools menu, choose Internet
Options. Then click the Advanced tab, and then
uncheck Show friendly HTTP error messages. This way, IE
will show whatever the server sends, even it if is error
messages. EVERY web developer should work with pretty error
messages turned off because the data IE hides is almost always
useful. I wish that customers reporting error messages would
work with pretty error messages turned off too!
-David
