RunTime Exception never gets caught by Seam in pages.xml

[infinity2heaven]

<exception class="javax.persistence.OptimisticLockException">
    <end-conversation/>
    <redirect view-id="/error.xhtml">
      <message severity="ERROR">Another user changed the same data, please try again</message>
    </redirect>
</exception>

When I test this use case, in the UI, instead of getting an error.xhtml page, I get the exception stack trace instead.

In fact, I had this working just a couple of days ago and I'm wondering what change I did in the codebase, that is bypassing pages.xml redirects

[mmichalek.mmichalek.micros-retail.com]

Does Seam's debug setting control this?

[infinity2heaven]

No. That's nothing to do with this. Like I said, I got this working a few days back.

[infinity2heaven]

This is interesting, as I can recreate this.

My save method is

@FlushMode(value=FlushModeType.COMMIT)
public void save() {
    FofPerformance fofPerformance = fofPerformanceDetail.getFofPerformance();                       
    entityManager.merge(fofPerformance);  
    //entityManager.flush();
    facesMessages.add("Monthly Data updated successfully by "+fofPerformanceDetail.getUpdatedBy());        
    }                           
}

If I comment uncomment entityManager.flush(), the opimtisticLockException doesn't propagate through pages.xml and I never get the error page. However without this, it works perfectly fine.

Any idea why?

[ellis2323.lmallet.oxalya.com]

RunTime exceptions have a different behaviour than Checked Exceptions (inherit from Exception). There is an interceptor of RunTime Exceptions in Seam which generate Rollbacks. RunTime exceptions could be managed as checked Exceptions if there is a @ApplicationException annotation on the runtime class.

I'm probably offtopic...