Error Handling - jbo25013 bug? - and workaround

Question

When I insert a record with a duplicate key and use errorpage.jsp to catch the exception(s), then every legitimate insert I do thereafter produces the same exceptions ie. JBO-26041, then JBO-25013.
A workaround for this is to surround my submission code in submit.jsp with a try {..)catch{} block.
i.e.
<%
try
%>
<jbo:PostChanges appid="Dbproject4Module" />
<jbo:Commit appid="Dbproject4Module" />
<%
catch(Exception exc)
out.println("<pre>");
exc.printStackTrace(new java.io.PrintWriter(out));
out.println("</pre>");
out.println("</BODY></HTML>");
return;
%>
This works fine.
However I have a number of queries:
i. Is this behavior of getting stuck on an error a bug in bc4j or perhaps in JDev's internal webserver?
ii. When errors are generated by errorpage.jsp, I first get JBO-26041, then if I press the refresh button on my browser I get JBO-25013, a more detailled message. I though that using
(oracle.jbo.JboException)exception.getDetails()
as errorpage.jsp does, would trap all the errors in the one page.
Any comments on the above behavior would be welcome.
thanks,
David Roberts

Answer 1

Repost