See my post here – https://forums.oracle.com/forums/message.jspa?messageID=10474315
There is a change in behaviour between 184.108.40.206 and 220.127.116.11 wrt exceptions in method activity. When a method activity is bound to a ADF BC method and an exception occurs, the error message is no longer displayed as a Faces message. I did raise this as an SR with Oracle but have since switched jobs and don’t have access to the SR.
Anyway, Frank Nimphius posted back on the forum with the response to the bug. Essentially, this was a bug fix in 18.104.22.168 so this is as expected. To render JBO exceptions as a Faces message, you will now need to create a custom exception handler. The sample code from the bug is below
ControllerContext context = ControllerContext.getInstance(); ViewPortContext currentRootViewPort = context.getCurrentViewPort(); Exception ex = currentRootViewPort.getExceptionData(); FacesContext fc = FacesContext.getCurrentInstance(); FacesMessage facesMessage = new FacesMessage(FacesMessage.SEVERITY_ERROR, "ADFc Exception Handler: " + ex.getMessage(), null); fc.addMessage(null, facesMessage);
There you go.