Exception Handling in ADF
Jdeveloper version 11.1.1.5.0
Use Case :
My application has :- 1 Jspx page ( testPage.jspx ) , 1 taskflow ( testExceptionFlow.xml ) , 1 pageFragment ( testOperation.jsff ).
I have employee table dragged as table on testOperation.jsff with 4 buttons :
1. Delete - Executes the VO's Delete action.
2. Commit - AM's commit operation ( through datacontrol )
3. CustomDeleteAndCommit - One method in VOImpl which deletes the currentRow and calls this.getDBTransaction().commit() method.
4. CustomCommitThroughBean - Action listener in beans calls the commit through operation binding.
I have secured my application and create two users in jazn.xml User1 and User2. Now both users are logged in to the application using different browser.
Both users can see employee with empId 100.
User1 selects a employee with empId 100 and clicks Delete button. Further clicks Commit button.
User2 selects the same employee with empId 100 and clicks Delete button. Further he can choose to commit through different options :
a) Commit
b) CustomCommitThroughBean
OR
CustomDeleteAndCommit
Obviously there will be jboException stating that row is already delete. When I am calling it through CustomCommitThroughBean operationBinding.getErrors() has errors, so I don't see error on UI.
I see a couple of posts about different ways of handling Exception :
[Using Exception Handler in an ADF Task Flow | https://blogs.oracle.com/ADFProgrammers/entry/using_exception_handler_in_an]
[Extending the ADF Controller exception handler | https://blogs.oracle.com/jdevotnharvest/entry/extending_the_adf_controller_exception_handler]
[Task Flow Exception Handler | http://adfpractice-fedor.blogspot.com/2011/12/task-flow-exception-handler-you-must.html]
[Exception Handling in adf (Part 1) | http://adfwithejb.blogspot.com/2012/05/exception-handling-in-adf-part-1.html ]
Which method of exception handling is applicable should be chosen ?
I just want to notify user about exception through some custom message and table should get refreshed for further operation.
My observations :
I get an error dialog in case :
Commit & CustomDeleteAndCommit
whereas no default error in case : CustomCommitThroughBean
I have uploaded my application [here | http://dl.dropbox.com/u/70986236/BlogApplication/OperationBindingExecuteErrorApp.zip ] . Want to implement exception handling in this application.
Thanks,
Rajdeep
Edited by: Rajdeep on Jul 26, 2012 9:45 PM
When you invoke an operation programmatically through an ADF OperationBinding, the eventual exception is not thrown to you but it is reported to the BindingContainer and the BindingContainer automatically adds a FacesMessage of ERROR severity to the FacesContext. If you have an <af:messages> tag in your ADF Faces page, this error message should be displayed automatically.
Dimitar
Similar Messages
-
Hi everybody,
I want to develop an application and need exception handling.
I have a helper application that contains this classes:
MyADFPhaseListener extends ADFPhaseListener that return this: return new MyFacesPageLifecycle(),
MyErrorHandler extends DCErrorHandlerImpl,
MyFacesPageLifecycle extends FacesPageLifecycle that contain this methods:
prepareModel(LifecycleContext ctx) that set my errorhandler with this: ctx.getBindingContext().setErrorHandler(new MyErrorHandler(true));
and
reportErrors(PageLifecycleContext ctx){
DCBindingContainer bc = (DCBindingContainer)ctx.getBindingContainer();
if (bc != null) {
ArrayList<Exception> exceptions =new ArrayList<Exception>();
exceptions = bc.getExceptionsList();
if (exceptions != null) {
/*handle exceptions*/
My problem is here:
when throw an exception in my app like this: throw new JboException("Don't do that.", "101", null);
after create pagelifecycle and calling prepareModel(), reporterros() dose not call....!!!
why?
Edited by: 859070 on May 15, 2011 9:35 PMwhen click a button and call action of this button.
please note:
My helper application and main application are apart. I deploy helper application to jar file and use this jar file in main application.
Maybe exceptions don`t send to reportErrors() method in MyPageLifeCycle class, because i create a test class like this:
public class test {
public static void main(String[] args) throws SQLException {
ArrayList<Exception> exss = new ArrayList<Exception>();
exss.add(new JboException("A fatal exception is occurred",
"103", null));
exss.add(new NullPointerException());
exss.add(new SQLException());
MyFacesPageLifecycle efpl =new MyFacesPageLifecycle();
efpl.errorReporter(exss);
Body of errorReporter(ArrayList<Exception>) method is like reportErrors(PageLifecycleContext) just parameter is different.
public void errorReporter(ArrayList<Exception> excs) {
if (excs != null) {
for (Exception exception: excs) {
if(exception instanceof JboException){
System.out.println("JBOException is occurred here: "+exception.getMessage());
else if(exception instanceof SQLException){
System.out.println("SQLException is occurred here");
else if(exception instanceof NullPointerException){
System.out.println("NullPointerException is occurred here");
else{
and this handle exceptions list. My opinion is that exceptions between different applications(helper and main) are lost. is this correct? -
Error exception handling in adf
hi how do i handle error exception in adf for exaple if i have validation/constraint in my database that no duplicate value must be entered in table. how can i display unique constraint error in more meangiful way so the user user can undestand it,am in jdeveloper 11.1.1.6.0
how can i show this error to user as error message oppose to this database error,this error happen if same user is added to same organisation twice but the same user can be added to other organisation,i what to display error message like "this user already belong to organisation xyz"Edited by: adf009 on 2013/03/11 9:49 AM
Edited by: adf009 on 2013/03/11 10:56 AM
Edited by: adf009 on 2013/03/11 4:26 PMi change the method to this
@Override
public void reportException(DCBindingContainer dCBindingContainer,
Exception ex) {
if (ex instanceof TxnValException) {
Object[] exceptions= ((TxnValException)ex).getDetails();
if(ex!=null){
for(int i=0;i<exceptions.length;i++){
if(ex instanceof RowValException){
this.reportException(dCBindingContainer, (Exception)ex);
else{
super.reportException(dCBindingContainer, (Exception)ex);
but is still not display error message in more meangful way
my DataBindings.cpx is
<?xml version="1.0" encoding="UTF-8" ?>
<Application xmlns="http://xmlns.oracle.com/adfm/application"
version="11.1.1.61.92" id="DataBindings" SeparateXMLFiles="false"
Package="uam.view" ClientType="Generic"
ErrorHandlerClass= "uam.view.CustomErrorHandler">
<definitionFactories>
<factory nameSpace="http://xmlns.oracle.com/adf/controller/binding"
className="oracle.adf.controller.internal.binding.TaskFlowBindingDefFactoryImpl"/>
<dtfactory className="oracle.adf.controller.internal.dtrt.binding.BindingDTObjectFactory"/>
</definitionFactories>
<pageMap>
<page path="/payment.jsff" usageId="uam_view_paymentPageDef"/>
<page path="/test.jspx" usageId="uam_view_testPageDef"/>
<page path="/security.jsff" usageId="uam_view_securityPageDef"/>
<page path="/pdetails.jsff" usageId="uam_view_pdetailsPageDef"/>
<page path="/odetails.jsff" usageId="uam_view_odetailsPageDef"/>
<page path="/opayment.jsff" usageId="uam_view_opaymentPageDef"/>
<page path="/members.jsff" usageId="uam_view_membersPageDef"/>
<page path="/suburb.jsff" usageId="uam_view_suburbPageDef"/>
<page path="/testsub.jspx" usageId="uam_view_testsubPageDef"/>
<page path="/WEB-INF/register-org-flow.xml#register-org-flow@CreateInsert"
usageId="uam_view_register_org_flow_register_org_flow_CreateInsertPageDef"/>
<page path="/SelectOrg.jsff" usageId="uam_view_SelectOrgPageDef"/>
<page path="/updateorg.jspx" usageId="uam_view_updateorgPageDef"/>
<page path="/OrgDetails.jsff" usageId="uam_view_OrgDetailsPageDef"/>
</pageMap>
<pageDefinitionUsages>
<page id="uam_view_paymentPageDef" path="uam.view.pageDefs.paymentPageDef"/>
<page id="uam_view_testPageDef" path="uam.view.pageDefs.testPageDef"/>
<page id="uam_view_securityPageDef"
path="uam.view.pageDefs.securityPageDef"/>
<page id="uam_view_pdetailsPageDef"
path="uam.view.pageDefs.pdetailsPageDef"/>
<page id="uam_view_odetailsPageDef"
path="uam.view.pageDefs.odetailsPageDef"/>
<page id="uam_view_opaymentPageDef"
path="uam.view.pageDefs.opaymentPageDef"/>
<page id="uam_view_membersPageDef" path="uam.view.pageDefs.membersPageDef"/>
<page id="uam_view_suburbPageDef" path="uam.view.pageDefs.suburbPageDef"/>
<page id="uam_view_testsubPageDef" path="uam.view.pageDefs.testsubPageDef"/>
<page id="uam_view_register_org_flow_register_org_flow_CreateInsertPageDef"
path="uam.view.pageDefs.register_org_flow_register_org_flow_CreateInsertPageDef"/>
<page id="uam_view_SelectOrgPageDef"
path="uam.view.pageDefs.SelectOrgPageDef"/>
<page id="uam_view_updateorgPageDef"
path="uam.view.pageDefs.updateorgPageDef"/>
<page id="uam_view_OrgDetailsPageDef"
path="uam.view.pageDefs.OrgDetailsPageDef"/>
</pageDefinitionUsages>
<dataControlUsages>
<dc id="OrgValidationBean" path="uam.view.OrgValidationBean"/>
<dc id="UAMUtil" path="uam.view.UAMUtil"/>
<BC4JDataControl id="UAMAppModuleDataControl1"
Package=uam.model.common"
FactoryClass="oracle.adf.model.bc4j.DataControlFactoryImpl"
SupportsTransactions="true" SupportsFindMode="true"
SupportsRangesize="true" SupportsResetState="true"
SupportsSortCollection="true"
Configuration="UAMAppModuleLocal" syncMode="Immediate"
xmlns="http://xmlns.oracle.com/adfm/datacontrol"/>
<BC4JDataControl id="AppModuleDataControl"
Package=uam.model"
FactoryClass="oracle.adf.model.bc4j.DataControlFactoryImpl"
SupportsTransactions="true" SupportsFindMode="true"
SupportsRangesize="true" SupportsResetState="true"
SupportsSortCollection="true"
Configuration="AppModuleLocal" syncMode="Immediate"
xmlns="http://xmlns.oracle.com/adfm/datacontrol"/>
<BC4JDataControl id="UpdAppModuleDataControl"
Package=uam.model.UpdOrgDetails"
FactoryClass="oracle.adf.model.bc4j.DataControlFactoryImpl"
SupportsTransactions="true" SupportsFindMode="true"
SupportsRangesize="true" SupportsResetState="true"
SupportsSortCollection="true"
Configuration="UpdAppModuleLocal" syncMode="Immediate"
xmlns="http://xmlns.oracle.com/adfm/datacontrol"/>
</dataControlUsages>
</Application>
even if i call class CustomExceptionHandler it does not work
{code}
i have recreated the problem using hr schema and i uploaded hear
http://www.datafilehost.com/download-9d37bd8a.html
Edited by: adf009 on 2013/03/11 5:20 PM -
Exception Handling in bounded taskflows - expected behaviour
Hi,
I'm currently reviewing exception handling in bounded task flows and some things does not seems to be very clear for me.
(q1) Does it make sense that a bounded task flow calls a method (via a method activity) defined on the page definition of another page (outside of the BTF) by using a #{data.xxxmyPageDef.myMethodName.execute} EL expression?
(q2) Is is correct to expect the application to execute the method marked as ExceptionHandler in the taskflow, whenever an exception occurs?
(q3) I created 5 different scenarios where I call a service method which throws an exception, from within a page fragment of the BTF.
(q3 – sc1) Call a service method through the binding layer of the current page (by using #{bindings.xxx.execute})
Result: A dialog containing the exception message appears.
This is what I expected. Althought, the exception handler method does not seems to be invoked.(q3 – sc2) Call a service method through a task flow method activity using #{bindings.xxx.execute}
Result: A dialog containing the exception message appears.
This is what I expected. Althought, the exception handler method does not seems to be invoked.(q3 – sc3) Call a service method through a task flow method activity using #{data.myPageFragementPagedef.xxx.execute} (accessing the pageDef of the page fragment)
Result: Nothing happens.
This is not what I expected. Although, the exception handler method does nog seems to be invoked, I expect the ADF Error Handler to create a FacesMessage.(q3 – sc4) Call a service method through a task flow method activity using #{data.myPageContainingThePageFragmentPageDef.xxx.execute} (accessing the page containing the BTF region)
Result: Nothing happens.
This is not what I expected. Although, the exception handler method does nog seems to be invoked, I expect the ADF Error Handler to create a FacesMessage. (q3 – sc5) Call a service method through a task flow method activity using #{data.aPageOutsideTheBTFPageDef.xxx.execute} (accessing a page outside the BTW)
Result: Nothing happens.
This is not what I expected. Although, the exception handler method does nog seems to be invoked, I expect the ADF Error Handler to create a FacesMessage. (q4) How can it be possible that – without an exception handler – exceptions occur when calling method activities, without the exceptions being translated to FacesMessages?
Thanks in advance,
Koen Verhulst
JDeveloper 11.1.1.4Koen,
+(q1) Does it make sense that a bounded task flow calls a method (via a method activity) defined on the page definition of another page (outside of the BTF) by using a #{data.xxxmyPageDef.myMethodName.execute} EL expression?+
No. Exceptions should be handled locally.
+(q2) Is is correct to expect the application to execute the method marked as ExceptionHandler in the taskflow, whenever an exception occurs?+
Only for exceptions that are before Render Response. The Render Response Phase is not handled in ADFc. So exceptions that occur in managed beans may fall through
+(q3) I created 5 different scenarios where I call a service method which throws an exception, from within a page fragment of the BTF.+
+(q3 – sc1) Call a service method through the binding layer of the current page (by using #{bindings.xxx.execute}) Result: A dialog containing the exception message appears.+
This is what I expected. Althought, the exception handler method does not seems to be invoked.
The binding layer has an error handler you can override in the DataBinings.cpx file
+(q3 – sc2) Call a service method through a task flow method activity using #{bindings.xxx.execute}+
Result: A dialog containing the exception message appears.
This is what I expected. Althought, the exception handler method does not seems to be invoked.
Again, you use the binding layer to invoke the service
+(q3 – sc3) Call a service method through a task flow method activity using #{data.myPageFragementPagedef.xxx.execute} (accessing the pageDef of the page fragment)+
Result: Nothing happens.
This is not what I expected. Although, the exception handler method does nog seems to be invoked, I expect the ADF Error Handler to create a FacesMessage.
Never use such a call. Its bad practice as there is no guarantee the container you reference is active. Always have the method call activity have its own binding defined when accessing a method call activity. I know there are lots of example floating aroundthat you #{data ...} and many are from 10.1.3. This should be avoided alltogether though
+(q3 – sc4) Call a service method through a task flow method activity using #{data.myPageContainingThePageFragmentPageDef.xxx.execute} (accessing the page containing the BTF region)+
Result: Nothing happens.
This is not what I expected. Although, the exception handler method does not seems to be invoked, I expect the ADF Error Handler to create a FacesMessage.
Again, this is not a proper use of the ADF framework.
+(q3 – sc5) Call a service method through a task flow method activity using #{data.aPageOutsideTheBTFPageDef.xxx.execute} (accessing a page outside the BTW)+
Result: Nothing happens. This is not what I expected. Although, the exception handler method does nog seems to be invoked, I expect the ADF Error Handler to create a FacesMessage.
accessing a page outside the BTW (!!!) This should ring a worst practices alarm on your laptop (obviously doesn't do it either)
+(q4) How can it be possible that – without an exception handler – exceptions occur when calling method activities, without the exceptions being translated to FacesMessages?+
Exceptions are not handled in a single place but stacked. The business service raises an exception and passes it to the binding layer if not handled. The binding layer handles the exception and if it can't passes it to ADFc. ADFc can handle this exception if it is not during Render Response.
Bottom line: There is no single point of exception handling. So as a recommendation for best practices
- Catch and handle exceptions as close as possible to their origins
- If things can go wrong, thy will - use try/catch blocks in managed beans
- Use an exception handling activity in all bounded task flows. In the case of task flow call activities being used exceptions can bubble up to the caller. However, this would take users out of their current application context
- Exceptions not handled in ADFc can be intercepted by overriding the application task flow exception handler (used by the exception handler activities). This would give you a chance e.g. to handle issues during Render Response
- Never fight the framework, never bend the framework: Don't use out of scope access to page definitions and resources. Exception handling is not a replacement for bad code practices (sorry for saying this, its not meant to be rude) :-)
Though I don't have a qualified numbers of bugs open for exception handling in ADF between 11.1.1.4 and now (and some that are open), but there are issues reported in this area. If there is something that really feels wrong, please go ahead and file a bug and provide a test case for development to have a look. The Render Response issue, for example is something we are aware of and that is in discussion (afaik knows, there is a change in exception handling in JSF 2 that may have an impact to what we can do in ADFc).
thanks
Frank -
ADF Task Flow Exception Handling
Hi ,
I tried a very simple thing for taskFlow exception handling.
I created a bounded task flow with a page fragment (View1.jsff) and another view which is the TaskFlow ExceptionHandler (error.jsff).
The view1.jsff has a button whose action is bound to the backing bean. In the backingBean method I deliberately do division by 0.
Since this is an unHandled exception, I would have expected the control to come to error.jsff. But, instead I am shown a pop up box with the error message.
Why is the control not getting redirected to error.jsff ?
Thanks.
S.Srivatsa SivanHi Frank , im having the same problem.
I want to handle exceptions that occur while navigating task flows (example: A user navigates to a task flow that he/she does not have view permission)
I tried using a view activity and method activity as the exception handler but none of them works, the exception is still not handles. It does not even navigate to the exception handler on the task flow.
on the view page i have:
<af:panelStretchLayout topHeight="50px" id="psl1">
<f:facet name="top">
<af:panelGroupLayout layout="scroll"
xmlns:af="http://xmlns.oracle.com/adf/faces/rich"
id="pgl1">
Error message:
<af:outputText value="#{controllerContext.currentRootViewPort.exceptionData.message}" id="ot2"/>
</af:panelGroupLayout>
</f:facet>
<f:facet name="center">
<af:outputText value="#{my_exception_Handler.stackTrace}" id="ot1"/>
<!-- id="af_one_column_header_stretched" -->
</f:facet>
</af:panelStretchLayout>
I tried getting the error message and stacktrace from the controllerContext via EL like this "#{controllerContext.currentRootViewPort.exceptionData.message}"
and from the controllerContext class in functions that i have declared in my_exception_Handler class like this
" ControllerContext ctx = ControllerContext.getInstance();
ViewPortContext vCtx = ctx.getCurrentViewPort();
if(vCtx.getExceptionData() != null){
StringWriter stringWriter = new StringWriter();
PrintWriter printWriter = new PrintWriter(stringWriter);
vCtx.getExceptionData().printStackTrace(printWriter);
return stringWriter.toString();"
But all this dont even matter because when the exception occurs on the task flow it does not navigate to the default exception handler.
thanks for your interest and help in advance.
Cyborg_0912 -
11g ADF TaskFlow Exception Handling in BPM
Hi Guys
BPM 11g
I have a human task that is implemented as an ADF task flow. I would like to be able to throw an exception from the ADF application and have it handled by the BPM process, does anyone know if this is possible or how I would do that?
At the moment I have an ADF error page - I could return an "error" outcome to the process from that but an error is an error and it feels right to show that in the process instead of a normal outcome.
anyone else worked through this?
cheers,
Stevehelp yourself with this thread - Re: Exception Handling
it should answer your question -
ADF Faces: Exception Handler activity ain't reraised
Hi there!
I'm using a Studio Edition Version 11.1.1.3.0 (Build JDEVADF_11.1.1.3.PS2_GENERIC_100408.2356.5660).
I've done this:
1. created a bounded task flow flow1 and added to it:
1.1 a vew activity view1 (the default activity) - shows an inputText field for a db column, for which there is a constraint;
1.2 a method call activity method1 - calls commit;
1.3 a view activity view2 - has an ouputText depicting an attribute's value for the same collection as that of inputText in view1;
1.4 a view activity errorView (marked as an exception handler) - displays a localizedMessage from the currentViewPort;
1.5 created for the view activities page fragments (with necessary fields and buttons).
2. linked them as follows:
2.1 view1 -*-> method1 -*-> view2;
2.2 errorView -*-> view1.
3. in the default unbounded task flow created a view activity main, a page file for it, and dropped onto the latter the flow1 as a region;
4. launched the app (as the table contains some data, the view1 displays first row in a row set);
5. entered into the view1 's field a non-violating value;
6. pressed a button (which has just an action property set to move to the method1 ) - everything's fine, we get to the view2;
6. rerun the app;
7. entered incorrect value, pressed the button - flow goes, as expected, to the errorView, which informs us the exception's details (JBO-...);
8. on the errorView page fragment pressed a button - we are now on the view1 page again;
9. left the wrong (violating) value (or changed it to another incorrect value, doesn't matter) and pressed the button again;
10. wow, we reached the view2, but, I guess, we hadn't to. Why so?
One must note, that in clauses 7 and 9, after pressing the button, there apears a popup, which advises us about an ORA-... error, that is, in step 9 the ADF Faces does receive the exception, but why it doesn't reraise the errorView, that's the question.
Though, when I change the method1 so, that it calls a bean's method, which always throws an IllegalArgumentException, then everything works as should to - we get to the infinite loop - view1 -> method1 -> errorView -> view1.
Or, when I extract view2 from flow1, and instead of the former insert return activity with End Transaction set to commit, and then wrap (i.e call) flow1 from a newly created bounded task flow flow2, and in main 's page replace flow1 with flow2 region, the result is quite different. The aforesaid popup with ORA- error arises, until one enters a non-violating value. That is in this case everything is good, except, that control never flows into the errorView.
And there is one more thing to note yet. When I've, namely method1, been calling a bean with the ever exception throwing method, the Integrated WLS's log was silent, but when the method1 was calling commit, then in the log we can see this twice:
<Utils><buildFacesMessage> ADF: Adding the following JSF error message: ORA-02290: check constraint CHECK(THE_USER.THE_CONSTRAINT) violated
java.sql.SQLIntegrityConstraintViolationException: ORA-02290: check constraint CHECK(THE_USER.THE_CONSTRAINT) violated
at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:85)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:206)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1035)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:194)
at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:953)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1224)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3386)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3467)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1350)
at oracle.jbo.server.OracleSQLBuilderImpl.doEntityDML(OracleSQLBuilderImpl.java:429)
at oracle.jbo.server.EntityImpl.doDML(EntityImpl.java:8044)
at oracle.jbo.server.EntityImpl.postChanges(EntityImpl.java:6373)
at oracle.jbo.server.DBTransactionImpl.doPostTransactionListeners(DBTransactionImpl.java:3172)
at oracle.jbo.server.DBTransactionImpl.postChanges(DBTransactionImpl.java:2980)
at oracle.jbo.server.DBTransactionImpl.commitInternal(DBTransactionImpl.java:2018)
at oracle.jbo.server.DBTransactionImpl.commit(DBTransactionImpl.java:2277)
at oracle.adf.model.bc4j.DCJboDataControl.commitTransaction(DCJboDataControl.java:1577)
at oracle.adf.model.binding.DCDataControl.callCommitTransaction(DCDataControl.java:1404)
at oracle.jbo.uicli.binding.JUCtrlActionBinding.doIt(JUCtrlActionBinding.java:1427)
at oracle.adf.model.binding.DCDataControl.invokeOperation(DCDataControl.java:2141)
at oracle.jbo.uicli.binding.JUCtrlActionBinding.invoke(JUCtrlActionBinding.java:730)
at oracle.adf.controller.v2.lifecycle.PageLifecycleImpl.executeEvent(PageLifecycleImpl.java:394)
at oracle.adfinternal.view.faces.model.binding.FacesCtrlActionBinding._execute(FacesCtrlActionBinding.java:252)
at oracle.adfinternal.view.faces.model.binding.FacesCtrlActionBinding.execute(FacesCtrlActionBinding.java:210)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.el.parser.AstValue.invoke(AstValue.java:157)
at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283)
at oracle.adf.controller.internal.util.ELInterfaceImpl.invokeMethod(ELInterfaceImpl.java:168)
at oracle.adfinternal.controller.activity.MethodCallActivityLogic.execute(MethodCallActivityLogic.java:161)
at oracle.adfinternal.controller.engine.ControlFlowEngine.executeActivity(ControlFlowEngine.java:989)
at oracle.adfinternal.controller.engine.ControlFlowEngine.doRouting(ControlFlowEngine.java:878)
at oracle.adfinternal.controller.engine.ControlFlowEngine.doRouting(ControlFlowEngine.java:777)
at oracle.adfinternal.controller.engine.ControlFlowEngine.routeFromActivity(ControlFlowEngine.java:551)
at oracle.adfinternal.controller.engine.ControlFlowEngine.performControlFlow(ControlFlowEngine.java:147)
at oracle.adfinternal.controller.application.NavigationHandlerImpl.handleAdfcNavigation(NavigationHandlerImpl.java:109)
at oracle.adfinternal.controller.application.NavigationHandlerImpl.handleNavigation(NavigationHandlerImpl.java:78)
at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:130)
at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:190)
at oracle.adf.view.rich.component.fragment.UIXRegion.broadcast(UIXRegion.java:148)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.broadcastEvents(LifecycleImpl.java:812)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:292)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:177)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:191)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:97)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:157)
at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:94)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:414)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:138)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:159)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)What I'm doing wrong? And how can I dismiss that popup, as it duplicates errorView and does not get messages from a custom message bundle?
Thanks in advance for any comments.
Yerzhan.Hi there!
I'm using a Studio Edition Version 11.1.1.3.0 (Build JDEVADF_11.1.1.3.PS2_GENERIC_100408.2356.5660).
I've done this:
1. created a bounded task flow flow1 and added to it:
1.1 a vew activity view1 (the default activity) - shows an inputText field for a db column, for which there is a constraint;
1.2 a method call activity method1 - calls commit;
1.3 a view activity view2 - has an ouputText depicting an attribute's value for the same collection as that of inputText in view1;
1.4 a view activity errorView (marked as an exception handler) - displays a localizedMessage from the currentViewPort;
1.5 created for the view activities page fragments (with necessary fields and buttons).
2. linked them as follows:
2.1 view1 -*-> method1 -*-> view2;
2.2 errorView -*-> view1.
3. in the default unbounded task flow created a view activity main, a page file for it, and dropped onto the latter the flow1 as a region;
4. launched the app (as the table contains some data, the view1 displays first row in a row set);
5. entered into the view1 's field a non-violating value;
6. pressed a button (which has just an action property set to move to the method1 ) - everything's fine, we get to the view2;
6. rerun the app;
7. entered incorrect value, pressed the button - flow goes, as expected, to the errorView, which informs us the exception's details (JBO-...);
8. on the errorView page fragment pressed a button - we are now on the view1 page again;
9. left the wrong (violating) value (or changed it to another incorrect value, doesn't matter) and pressed the button again;
10. wow, we reached the view2, but, I guess, we hadn't to. Why so?
One must note, that in clauses 7 and 9, after pressing the button, there apears a popup, which advises us about an ORA-... error, that is, in step 9 the ADF Faces does receive the exception, but why it doesn't reraise the errorView, that's the question.
Though, when I change the method1 so, that it calls a bean's method, which always throws an IllegalArgumentException, then everything works as should to - we get to the infinite loop - view1 -> method1 -> errorView -> view1.
Or, when I extract view2 from flow1, and instead of the former insert return activity with End Transaction set to commit, and then wrap (i.e call) flow1 from a newly created bounded task flow flow2, and in main 's page replace flow1 with flow2 region, the result is quite different. The aforesaid popup with ORA- error arises, until one enters a non-violating value. That is in this case everything is good, except, that control never flows into the errorView.
And there is one more thing to note yet. When I've, namely method1, been calling a bean with the ever exception throwing method, the Integrated WLS's log was silent, but when the method1 was calling commit, then in the log we can see this twice:
<Utils><buildFacesMessage> ADF: Adding the following JSF error message: ORA-02290: check constraint CHECK(THE_USER.THE_CONSTRAINT) violated
java.sql.SQLIntegrityConstraintViolationException: ORA-02290: check constraint CHECK(THE_USER.THE_CONSTRAINT) violated
at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:85)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:206)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1035)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:194)
at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:953)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1224)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3386)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3467)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1350)
at oracle.jbo.server.OracleSQLBuilderImpl.doEntityDML(OracleSQLBuilderImpl.java:429)
at oracle.jbo.server.EntityImpl.doDML(EntityImpl.java:8044)
at oracle.jbo.server.EntityImpl.postChanges(EntityImpl.java:6373)
at oracle.jbo.server.DBTransactionImpl.doPostTransactionListeners(DBTransactionImpl.java:3172)
at oracle.jbo.server.DBTransactionImpl.postChanges(DBTransactionImpl.java:2980)
at oracle.jbo.server.DBTransactionImpl.commitInternal(DBTransactionImpl.java:2018)
at oracle.jbo.server.DBTransactionImpl.commit(DBTransactionImpl.java:2277)
at oracle.adf.model.bc4j.DCJboDataControl.commitTransaction(DCJboDataControl.java:1577)
at oracle.adf.model.binding.DCDataControl.callCommitTransaction(DCDataControl.java:1404)
at oracle.jbo.uicli.binding.JUCtrlActionBinding.doIt(JUCtrlActionBinding.java:1427)
at oracle.adf.model.binding.DCDataControl.invokeOperation(DCDataControl.java:2141)
at oracle.jbo.uicli.binding.JUCtrlActionBinding.invoke(JUCtrlActionBinding.java:730)
at oracle.adf.controller.v2.lifecycle.PageLifecycleImpl.executeEvent(PageLifecycleImpl.java:394)
at oracle.adfinternal.view.faces.model.binding.FacesCtrlActionBinding._execute(FacesCtrlActionBinding.java:252)
at oracle.adfinternal.view.faces.model.binding.FacesCtrlActionBinding.execute(FacesCtrlActionBinding.java:210)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.el.parser.AstValue.invoke(AstValue.java:157)
at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283)
at oracle.adf.controller.internal.util.ELInterfaceImpl.invokeMethod(ELInterfaceImpl.java:168)
at oracle.adfinternal.controller.activity.MethodCallActivityLogic.execute(MethodCallActivityLogic.java:161)
at oracle.adfinternal.controller.engine.ControlFlowEngine.executeActivity(ControlFlowEngine.java:989)
at oracle.adfinternal.controller.engine.ControlFlowEngine.doRouting(ControlFlowEngine.java:878)
at oracle.adfinternal.controller.engine.ControlFlowEngine.doRouting(ControlFlowEngine.java:777)
at oracle.adfinternal.controller.engine.ControlFlowEngine.routeFromActivity(ControlFlowEngine.java:551)
at oracle.adfinternal.controller.engine.ControlFlowEngine.performControlFlow(ControlFlowEngine.java:147)
at oracle.adfinternal.controller.application.NavigationHandlerImpl.handleAdfcNavigation(NavigationHandlerImpl.java:109)
at oracle.adfinternal.controller.application.NavigationHandlerImpl.handleNavigation(NavigationHandlerImpl.java:78)
at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:130)
at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:190)
at oracle.adf.view.rich.component.fragment.UIXRegion.broadcast(UIXRegion.java:148)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.broadcastEvents(LifecycleImpl.java:812)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:292)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:177)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:191)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:97)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:157)
at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:94)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:414)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:138)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:159)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)What I'm doing wrong? And how can I dismiss that popup, as it duplicates errorView and does not get messages from a custom message bundle?
Thanks in advance for any comments.
Yerzhan. -
Using Exception Handler in an ADF Task Flow
Hi folks.
Today I gave a try on Exception Handling. while i go through the blog.
https://blogs.oracle.com/ADFProgrammers/entry/using_exception_handler_in_an
I cant able to attain the Solution 2: Re-Routing the task flow to display an error page As per the Figure 9 i make it out.
but it is not navigating error.jsff.
Taskflow return is not working i hope. only Exception thrown only happens from method.
anyone help me out. what I'm missing ?
- jdev 11.1.1.6.0hi,
is there anyone help me out of this issue. -
How to display the 500-internal server error on the Exception Handler page
Hello
My situation is as follows : JDev 11.1.1.0.2, ADF fusion application, one unbounded task flow containing 2 view pages view1.jspx and error.jspx
The error jspx is marked as the exception handler.
When an error occurs (typically a 500-Internal Server Error) the error.jspx is correctly displayed and shows our message such as 'Don't panic, please call our tech support'
What I would like to do is to display the actual error stack on this page along with our message.
I've searched around and I can't find how to either get the error stack in a bean or what EL expression should be used to get the error stack.
Can anybody help ?
Best Regards
Paul
SwitzerlandThe error will be the same, but the stack trace will be different, such as
Error 500--Internal Server Error
oracle.adf.controller.security.AuthorizationException: ADFC-0619: Echec de la vérification des autorisations : '/view1.jspx' 'VIEW'.
at oracle.adf.controller.internal.security.AuthorizationEnforcer.handleFailure(AuthorizationEnforcer.java:145)
at oracle.adf.controller.internal.security.AuthorizationEnforcer.checkPermission(AuthorizationEnforcer.java:124)
at oracle.adfinternal.controller.state.ControllerState.initializeUrl(ControllerState.java:639)
at oracle.adfinternal.controller.state.ControllerState.synchronizeStatePart2(ControllerState.java:449)
at oracle.adfinternal.controller.application.SyncNavigationStateListener.afterPhase(SyncNavigationStateListener.java:44)
at oracle.adfinternal.controller.lifecycle.ADFLifecycleImpl$PagePhaseListenerWrapper.afterPhase(ADFLifecycleImpl.java:529)
at oracle.adfinternal.controller.lifecycle.LifecycleImpl.internalDispatchAfterEvent(LifecycleImpl.java:118)
at oracle.adfinternal.controller.lifecycle.LifecycleImpl.dispatchAfterPagePhaseEvent(LifecycleImpl.java:166)
at oracle.adfinternal.controller.faces.lifecycle.ADFPhaseListener$PhaseInvokerImpl.dispatchAfterPagePhaseEvent
What I would like is to display the above stack trace on the page marked as the exception handler....
Regards
Paul -
How to set up global exception handling to provide user friendly messages to user?
AFAIK there is no real global exception handing available for now in ADF. So I need some "tutorials" about exception handling in:
- Model
- Controller
- View
Thx
Regards
Zmedarefer this
http://blogs.oracle.com/groundside/entry/adventures_in_adf_logging_part
controller
http://blogs.oracle.com/jdevotnharvest/entry/extending_the_adf_controller_exception_handler
http://andrejusb.blogspot.com/2011/03/exception-handler-for-method-calls_19.html
http://my.safaribooksonline.com/book/databases/oracle/9780071622547/introduction-to-oracle-adf-task-flows/ch04lev1sec7
http://my.safaribooksonline.com/book/databases/oracle/9780071622547/working-with-unbounded-and-bounded-oracle-adf-task-flows/169 -
Exception Handling in Web Center for UI related Errors not working.
Hi Guys,
I have implemented Error Handling in ADF Application with Custom Model Exception Handler ( which is "CustomExceptionHandler extends DCErrorHandlerImpl") to catch all Model Layer Exception and to customize those error messages.
I have implemented Error Handling in ADF Application with Custom View Exception Handler ( which is "CustomViewErrorHandler extends oracle.adf.view.rich.context.ExceptionHandler";) to catch all View Layer Exception and to customize those error messages.
The design for this is , in Model Custom Exception Handler i find the exception message in "public String getDisplayMessage(BindingContext bindingContext,Exception exception) " method and throw RuntimeException to pass this exception to Custom View Layer Exception , so that i can handle all the exception @ View Layer it self .
In the View Layer Exception Handler i am navigating to specific error page using
String contextPath = ((HttpServletRequest)FacesContext.getCurrentInstance().getExternalContext().getRequest()).getContextPath();
ExternalContext ectx = facesContext.getExternalContext();
ectx.redirect.
All these things absolutly working in ADF Application for all the exception ( Model , View ) and i am successfully navigating to error page.
Problem :
When i implement the same thing in Webcenter Application ( Model Custom Exception Handler and View Custom Exception Handler), Model Part is working as expected , but View Custom Exception Handler is not all calling .
i am assuming that ,this View Custom Exception Handler (CustomViewErrorHandler extends oracle.adf.view.rich.context.ExceptionHandler) works only for JSF Life cycle
"Allows frameworks to intercept otherwise unhandled exceptions thrown during the JSF lifecycle. ExceptionHandlers can be registered by adding a service file with a class name at META-INF/services/oracle.adf.view.rich.context.ExceptionHandler." from http://jdevadf.oracle.com/adf-richclient-demo/docs/apidocs/oracle/adf/view/rich/context/ExceptionHandler.html";
As Webcenter Portal uses ADF Life Cycle this Exception Handler is not calling , i am not sure.
if any one has any idea please let me know .
Thanks
Annapareddy Srinivasrao
Edited by: Srinivasrao Annapareddy on May 22, 2013 12:06 PMi used runtime exception along with the wdwsmodel exception
-
Exception handler activity doesn't execute
I have an exception handler in my bounded task flow but it not always executes when an error is raised by some of the BTF activities.
In my application I'm having a problem with connections closed.
I don't know if the database, the firewall or who is closing connections but sometimes I get an error in the logs "oracle.jbo.JboException: JBO-29000: Se ha obtenido una excepción inesperada: java.sql.SQLRecoverableException, mensaje=Conexión cerrada" translation "oracle.jbo.JboException: JBO-29000: Un unexpected exception has been raised: java.sql.SQLRecoverableException, message=Closed connection".
That is bothering me specially because my task flow continues execution despite of the error. ADF opens the connection and then continues execution. This is fatal because previous updating in the entity objects is lost and the consequence is very bad.
Well, I have tried to insert an exception handler in my task flow in order to capture this errors and then stop execution of the task flow.
Currently, I'm more upset because of task flow continues execution after the connection closed error that for the error itself.
The problem is that sometimes the connection closed appears in the log window but the exception handler is not executed. Sometimes yes, some others no.
In order to test I'm forcing the error manually killing the sessions in the server.
Any help for any of both problems ? (1- BTF continuing execution after this error raising and 2-Why the exception handler doesn't always execute when a java error stack appears in the log window).
Thank you.this might be caused by a bug I found too causing eventhandlers not to work, the work round in your case would be:
blar blar blar
</variables>
<!-- start work round --><scope><!-- end work round -->
<faultHandlers>
blar blar blar
blar blar blar
</sequence>
<!-- start work round --></scope><!-- end work round -->
</process>
i.e. what I'm saying is that top level handler don't work since they are ignored by the engine because they are not in a scope. Try it and see.... -
Bounded Taskflow Exception Handler not working with Page Fragements
I have one bounded - taskflow task-flow-definition
<?xml version="1.0" encoding="windows-1252" ?>
<adfc-config xmlns="http://xmlns.oracle.com/adf/controller" version="1.2">
<task-flow-definition id="task-flow-definition">
<default-activity>view1</default-activity>
<managed-bean>
<managed-bean-name>backing_main</managed-bean-name>
<managed-bean-class>view.backing.Main</managed-bean-class>
<managed-bean-scope>pageFlow</managed-bean-scope>
</managed-bean>
<managed-bean>
<managed-bean-name>backing_view1</managed-bean-name>
<managed-bean-class>view.backing.View1</managed-bean-class>
<managed-bean-scope>pageFlow</managed-bean-scope>
</managed-bean>
<managed-bean>
<managed-bean-name>backing_view2</managed-bean-name>
<managed-bean-class>view.backing.View2</managed-bean-class>
<managed-bean-scope>pageFlow</managed-bean-scope>
</managed-bean>
<exception-handler>view2</exception-handler>
<view id="view1">
<page>/view1.jsff</page>
</view>
<view id="view2">
<page>/view2.jsff</page>
</view>
<use-page-fragments/>
</task-flow-definition>
</adfc-config>view1.jsff contains one command button, which calls one ActionListener
<?xml version='1.0' encoding='windows-1252'?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
<af:commandButton text="commandButton 1" actionListener="#{pageFlowScope.backing_view1.callMyFunction}"
binding="#{pageFlowScope.backing_view1.commandButton1}"
id="commandButton1"/>
<!--oracle-jdev-comment:auto-binding-backing-bean-name:backing_view1-->
</jsp:root>view1.java callMyFunction throws an Exception
public void callMyFunction(ActionEvent event) throws Exception{
throw new Exception();
}view2.jsff is an exception handler
<?xml version='1.0' encoding='windows-1252'?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
<af:activeOutputText value="Exception Occured"
binding="#{pageFlowScope.backing_view2.activeOutputText1}"
id="activeOutputText1"
inlineStyle="font-size:xx-large; color:red;"/>
<!--oracle-jdev-comment:auto-binding-backing-bean-name:backing_view2-->
</jsp:root>above taskflow is dragged-drop as a Region in one file main.jspx
<?xml version='1.0' encoding='windows-1252'?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
<jsp:directive.page contentType="text/html;charset=windows-1252"/>
<f:view>
<af:document binding="#{pageFlowScope.backing_main.document1}"
id="document1">
<af:form binding="#{pageFlowScope.backing_main.form1}" id="form1">
<af:region value="#{bindings.taskflowdefinition1.regionModel}"
id="taskf1"
binding="#{pageFlowScope.backing_main.taskf1}"/>
</af:form>
</af:document>
</f:view>
<!--oracle-jdev-comment:auto-binding-backing-bean-name:backing_main-->
</jsp:root>*pressing a commandButton on view1.jsff throws an Exception as expected but does not go to exceptionHandler [view2.jsff]*
However, this does work with Bounded Task-Flow without page fragments , view1.jspx contains one button, calling one method which throws an Exception,
view2.jspx is an Exception Handler, and in this case it redirects to the view2.jspx [error page]
any ideas?
thanksHi,
Pretty much. However, you got the event part wrong, which is mostly my fault here. First, let put down some general JSF facts about event handling.
1. http://java.sun.com/javaee/5/docs/api/javax/faces/component/UIComponent.html#queueEvent(javax.faces.event.FacesEvent)
2. So, basically, queuing an event on a component means queuing it on its parent until you reach the UIViewRoot that will really actually queue it. That strategy allows iterating components to intercept event queued on their children to record the row index as well so that the data model can be synchronized correctly during the broadcast phase (see http://java.sun.com/javaee/5/docs/api/javax/faces/component/UIData.html#queueEvent(javax.faces.event.FacesEvent) and http://java.sun.com/javaee/5/docs/api/javax/faces/component/UIData.html#broadcast(javax.faces.event.FacesEvent))
3. Exceptions that aren't handled by the exception handler are thrown during broadcast or various process* methods.
So, the catch component must leverage these facts to intercept events queued on its children (by overriding queueEvent method) wrapping the original event in a custom on that flag the catch component itself as the source of the event. The result will be that the broadcast method of the catch component will be called to handle the event. The broadcast method must then unwrap the event (to get the original event), gets the original source, then call originalSource.broadcast(originalEvent) within a try-catch block.
Does it make any more sense put that way? Note that it's an obscure part of JSF so I cannot make it incredibly simple either.
Regards,
~ Simon -
Custom exception problems with ADF framework
Hi,
I have problems with the exception handling in an web service Java class (POJO).
In this class I throw my own exception WsException-class which extends the normal Exception-class.
The class WebservicesAppModule extends the oracle.jbo.ApplicationModule.
In the following I first describe the web service class and then the three tests a)-c).
In test b) you can find my main problem.
Web service Java class (POJO):
public Element check(Element element) throws WsException{
WebservicesAppModule am = null;
try {
// 1) system error
// if I comment the next line out, then am = null and a NullPointerException is thrown which appear as NullPointerException in the SOAP response
am = (WebservicesAppModule)Configuration.createRootApplicationModule(_am,_cf);
if(value == null){
// 2) application error
WsException wsex = new WsException();
wsex.addErrorCode(WsException.C_INVALID_BANK_CONNECTION);
throw wsex;
} else if (value2 == null){
// 3) explicit system error
throw new NullPointerException();
}catch(WsException wsex){
// 4) application error
throw wsex;
}catch(Throwable ex){
// 5) system error
log.debug("Technischer Fehler", ex);
WsException wsex = new WsException("system error");
wsex.addErrorCode(WsException.C_NOK);
throw wsex;
} finally {
if (_am != null) {
Configuration.releaseRootApplicationModule(am, false);
Test a):
- The WebservicesAppModule is initialized (1)
- value = null, so the process run in the "application error" if-block (2)
- The WsException is thrown and catched in the "application error" catch-block (4)
The SOAP repsonse is okay:
--- Response ---
HTTP/1.1 100 Continue
Server: Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)
Date: Thu, 20 Jul 2006 09:43:39 GMT
HTTP/1.1 500 Internal Server Error
Date: Thu, 20 Jul 2006 09:43:55 GMT
Server: Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)
Content-Length: 520
Connection: Close
Content-Type: text/xml; charset=utf-8
<?xml version = '1.0' encoding = 'UTF-8'?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server.Exception:</faultcode>
<faultstring>[11000, 10001] [de.test.webservices.WsException]</faultstring>
<faultactor>/app-Webservices-context-root/WebServices</faultactor>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Test b):
- The WebservicesAppModule is NOT initialized (the line is comment out) (1)
- The process run in system error catch-block (5)
In the SOAP repsonse I expected the following <faultstring> (like in test c) )
<faultstring>system error: [10000] [de.test.webservices.WsException]</faultstring>
and not
<faultstring> [java.lang.NullPointerException]</faultstring>
What´s the problem?
--- Response ---
HTTP/1.1 100 Continue
Server: Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)
Date: Thu, 20 Jul 2006 08:59:12 GMT
HTTP/1.1 500 Internal Server Error
Date: Thu, 20 Jul 2006 09:01:02 GMT
Server: Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)
Content-Length: 506
Connection: Close
Content-Type: text/xml; charset=utf-8
<?xml version = '1.0' encoding = 'UTF-8'?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server.Exception:</faultcode>
<faultstring> [java.lang.NullPointerException]</faultstring>
<faultactor>/app-Webservices-context-root/WebServices</faultactor>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Test c):
- The WebservicesAppModule is initialized (1)
- value != null, so the process run to the next if-block (2)
- value2 == null, so the process run in the "explicit system error" (3)
- The WsException is thrown and catched in the "system error" catch-block (5)
This test shows that not the NullPointerException of Test b) is the problem.
This response is expected in Test b).
--- Response ---
HTTP/1.1 100 Continue
Server: Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)
Date: Thu, 20 Jul 2006 13:53:46 GMT
HTTP/1.1 500 Internal Server Error
Date: Thu, 20 Jul 2006 13:54:19 GMT
Server: Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)
Content-Length: 533
Connection: Close
Content-Type: text/xml; charset=utf-8
<?xml version = '1.0' encoding = 'UTF-8'?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server.Exception:</faultcode>
<faultstring>system error: [10000] [de.test.webservices.WsException]</faultstring>
<faultactor>/app-Webservices-context-root/WebServices</faultactor>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
What is the cause for the false <faultstring> in test b)? Where set the the ADF framework the NullPointerException and how can I avoid that?
Thanks and best regards,
TobiasHi,
I have problems with the exception handling in an web service Java class (POJO).
In this class I throw my own exception WsException-class which extends the normal Exception-class.
The class WebservicesAppModule extends the oracle.jbo.ApplicationModule.
In the following I first describe the web service class and then the three tests a)-c).
In test b) you can find my main problem.
Web service Java class (POJO):
public Element check(Element element) throws WsException{
WebservicesAppModule am = null;
try {
// 1) system error
// if I comment the next line out, then am = null and a NullPointerException is thrown which appear as NullPointerException in the SOAP response
am = (WebservicesAppModule)Configuration.createRootApplicationModule(_am,_cf);
if(value == null){
// 2) application error
WsException wsex = new WsException();
wsex.addErrorCode(WsException.C_INVALID_BANK_CONNECTION);
throw wsex;
} else if (value2 == null){
// 3) explicit system error
throw new NullPointerException();
}catch(WsException wsex){
// 4) application error
throw wsex;
}catch(Throwable ex){
// 5) system error
log.debug("Technischer Fehler", ex);
WsException wsex = new WsException("system error");
wsex.addErrorCode(WsException.C_NOK);
throw wsex;
} finally {
if (_am != null) {
Configuration.releaseRootApplicationModule(am, false);
Test a):
- The WebservicesAppModule is initialized (1)
- value = null, so the process run in the "application error" if-block (2)
- The WsException is thrown and catched in the "application error" catch-block (4)
The SOAP repsonse is okay:
--- Response ---
HTTP/1.1 100 Continue
Server: Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)
Date: Thu, 20 Jul 2006 09:43:39 GMT
HTTP/1.1 500 Internal Server Error
Date: Thu, 20 Jul 2006 09:43:55 GMT
Server: Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)
Content-Length: 520
Connection: Close
Content-Type: text/xml; charset=utf-8
<?xml version = '1.0' encoding = 'UTF-8'?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server.Exception:</faultcode>
<faultstring>[11000, 10001] [de.test.webservices.WsException]</faultstring>
<faultactor>/app-Webservices-context-root/WebServices</faultactor>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Test b):
- The WebservicesAppModule is NOT initialized (the line is comment out) (1)
- The process run in system error catch-block (5)
In the SOAP repsonse I expected the following <faultstring> (like in test c) )
<faultstring>system error: [10000] [de.test.webservices.WsException]</faultstring>
and not
<faultstring> [java.lang.NullPointerException]</faultstring>
What´s the problem?
--- Response ---
HTTP/1.1 100 Continue
Server: Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)
Date: Thu, 20 Jul 2006 08:59:12 GMT
HTTP/1.1 500 Internal Server Error
Date: Thu, 20 Jul 2006 09:01:02 GMT
Server: Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)
Content-Length: 506
Connection: Close
Content-Type: text/xml; charset=utf-8
<?xml version = '1.0' encoding = 'UTF-8'?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server.Exception:</faultcode>
<faultstring> [java.lang.NullPointerException]</faultstring>
<faultactor>/app-Webservices-context-root/WebServices</faultactor>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Test c):
- The WebservicesAppModule is initialized (1)
- value != null, so the process run to the next if-block (2)
- value2 == null, so the process run in the "explicit system error" (3)
- The WsException is thrown and catched in the "system error" catch-block (5)
This test shows that not the NullPointerException of Test b) is the problem.
This response is expected in Test b).
--- Response ---
HTTP/1.1 100 Continue
Server: Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)
Date: Thu, 20 Jul 2006 13:53:46 GMT
HTTP/1.1 500 Internal Server Error
Date: Thu, 20 Jul 2006 13:54:19 GMT
Server: Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)
Content-Length: 533
Connection: Close
Content-Type: text/xml; charset=utf-8
<?xml version = '1.0' encoding = 'UTF-8'?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server.Exception:</faultcode>
<faultstring>system error: [10000] [de.test.webservices.WsException]</faultstring>
<faultactor>/app-Webservices-context-root/WebServices</faultactor>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
What is the cause for the false <faultstring> in test b)? Where set the the ADF framework the NullPointerException and how can I avoid that?
Thanks and best regards,
Tobias -
How to used exception handler ?
hi,
i am facing ADF-Faces 60003 exception in my project .i searched this problem they are saying this is bugs. i am using jdeveloper 11.1.1.3 . this message is coming in pop -up.to hiding this message i am thinking to implement exception handler .
is this possible to handle ?for exception handler , i created a class which contains following code
public class Eception extends ExceptionHandler{
public Eception() {
super();
public void handleException(FacesContext facesContext, Throwable throwable,
PhaseId phaseId) {
System.out.println("------------------------------");
String error_message;
error_message = throwable.getMessage();
//check error message and handle it if you can
System.out.println("===================="+error_message+"-------------------------"+phaseId);
and also i created a text file name oracle.adf.view.rich.context.Exceptionhandler and pasted in .adf\META-INF\services folder .
but still my handleException is not triggering .i do not know why ?
is there any other step .please let me know where is problem .
thanks
Edited by: ADFORCLE on Oct 27, 2011 1:28 PMany how i am able to called my handler method.name is handler file is not correct.after resolving this problem i am facing new problem.suppose right now i am in A page. if i navigate to different pages B . all are required validation message of page B is showing .even though it's first jsf life cycle phase .
Maybe you are looking for
-
How to perform 'block selection' in table control?
Hi, I'm looking for an easy way to implement block selection in a table control (i.e. select one line, hit 'block select' button, select a second line, hit 'block select' button again, and all lines between first and last are selected). I'm currently
-
Can i sync my iphone/mobile me account to two different macs
I've got two macs now in the house! The first one I bought was such a nice conversion from windows that I replaced the family computer with a mac as well. So can I hook up my mobile me/iphone up on my other computer as well without any weird issues b
-
Sending command strings to a Sorensen (Ametek / Xantrex) power supply model XDL 35-5TP
Hi all, I am using the above mentioned power suply to control test units during end of line tests. I can do all the normal funtions through the manufacturers supplied library of vi's. The problem is, I need to make sure the voltage being seen by th
-
Why cant I export or save keynote as powerpoint?
Why cant I export or save keynote as powerpoint?
-
Hi All, I uploaded a file in shared components , how we can download that file whcih has been uploaded in shared componets. and also let me know can we upload that file with the same extension. Thanks, Seshagiri.