Hi, I have the following problem surface recently which I _think_ is caused by an upgrade from Struts 1.1 to 1.2.4. If an .jsp file containing an error (not the tag <html:errors/> but a error like <logic:redirect... > (note the missing closing element /> )) is called, I get an exception (org.apache.jasper.JasperException: /index.jsp(1,35) Unterminated <logic:redirect> tag) displayed in the browser. If a .jsp file with a similar error ist part of a tiles-based page, I only get a blank page. This makes debugging the .jsp pages rather tedious. I am sure that some weeks ago I would also get an error message in the tile-based page.
I said I think the problem was caused by an upgrade to 1.2.4 since I haven't worked on the tiles based jsp pages for some time and I might have changed something else in between as well. But looking through my version control I found no change that should have changed the behaviour of Struts, Tomcat (4.1) or Jasper. By the way, this is an interesting problem because it only occurs when working with broken code, something one (or at least I) does not normally test in the standard testing frameworks. One does not test that broken code always breaks in the same way but rather just fixes the problem. Any ideas? Regards, Ulrich Elsner --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
