Task flow exception handler

Hi all,
I'm trying to specify a method activity as an exception handler in the adfc-config. The problem is if I specify a view activity or a bounded task flow as the exception handler then it works fine, but if the exception handler is a method activity then it is not recognized. What could be the cause?. I need to execute a method when an exception occurs.
Version: 11.1.2.0
Edited by: NewBee on Apr 23, 2013 10:37 AM

Hi,
there should not be a problem with this and I recently did the same with JDeveloper 11g R2 (not sure which version of JDeveloper you use because you did not share this information). I assume you just marked the method activity as an exception handler without any other configuration? If so then set a break point to the managed bean method that you access from the method activity to see if it actually stops there. Also note that not all exceptions are handled by the controller exception handler. E.g an exception during render response phase (typically an exception in a managed bean) is not handled by the controller. Also you need to avoid the managed bean that handles the exception to itself throw one. This however you will see when debugging the bean.
Frank

Similar Messages

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 Sivan

Hi 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"/>

</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

Task-flow exception only cought first time

We're working on a larger scale application, that relies heavily on PL/SQL. Therefor we throw a lot of jboexceptions in our applciations. FK, UK and other validations throw an exception in the base, and are thrown as jboexceptions from the java level.
The problem is, that the exception is only shown for the user, once per in each running task flow. It looks alot like this issue: http://java.net/jira/browse/ADFEMG-18
The exception is vissibe in the log file.
I'm running JDeveloper 11.1.1.5.0
Is there a fix?

Hi,
the fix starts with you providing us more information about your error handling process.
Have you verified the problem to reproduce e.g in 11.1.1.6?
Does the problem reproduce in a test case ?
The EMG bug you reference says that the problem doesn't reproduce in 11.1.1.6, so the fix would be to upgrade to 11.1.1.6 if it is the same issue, or work through customer support to get a backport patch in case you cannot migrate
Frank

Task Flow Transaction Handling Inconsistent between JDeveloper R1 & R2.

We have a solution developed using Jdeveloper 11.1.2.1.0.
To describe the use case I will use the HR schema.
The user must be able to view Regions and navigate to Countries and Locations in a hierarchical way. At each level he must be allowed to view and maintain the detail of the current record at that level. The user must also be able to navigate directly to a level and perform a search to view the data and from there be allowed to to view and maintain the detail of the current record at that level.
So I have created the following design to achieve this and take into consideration that I need to reuse my task flows that maintain the data.
Business Services (Model Project)
1. HierarchyAM, containing Read Only VO’s of the various levels nested by association/view link.
2. Region + Countries + Locations
3. Search#Level#AM, A separate AM for each level, containing the Read Only VO per level.
4. Maintain#Level#AM, A Separate AM for each level, containing an updateable VO per level.
UI (View Controller Project)
I created the following BTF’s (To try and keep the post short as possible I will only provide detail for a single level to explain the issues)
*1. HiererchyBTF*
a.     Contains a fragment.
b.     Added RegionHierarchyBtf, CountryHierarchyBTF, LocationHierarchyBTF to the above fragment as dynamic regions.
c.     Task flow transaction <No Controller Transaction>, isolated.
*2. RegionHierarchyBTF. (The same BTF’s are created for each level in the hierarchy)*
a.     Contains a fragment.
b.     Exposed HierarchyAM<RegionRoVO>
c.     Task flow transaction <No Controller Transaction>, shared.
d.     Includes a call to the EditRegionBTF.
*3. SearchRegionBTF (The same BTF’s are created for each level in the hierarchy)*
a.     Contains a fragment.
b.     Exposed SearchRegionAM<RegionRoVO>
c.     Task flow transaction <No Controller Transaction>, isolated.
d.     Includes a call to the EditRegionBTF.
*4. EditRegionBTF*
a.     Contains a fragment.
b.     Exposed MaintainRegionAM<RegionVO>
c.     Task flow transaction <Use Existing Transaction if Possible>, isolated.
Runtime behaviour with above configuration.
1.     Running the HiererchyBTF and navigation the levels works in all versions.
2.     Calling an edit BTF allows me to edit the current record and successfully commit the data in all versions.
3.     Calling an edit BTF for the same record immediately thereafter, allows me to edit the record and commit the data successfully in all versions.
4.     Running any of search BTF’s and calling the edit BTF works in all versions.
Runtime behaviour and changing the EditRegionBTF task flow transaction to Shared.
1.     Running the HiererchyBTF and navigation the levels works in all versions.
2.     Calling an edit BTF allows me to edit the current record in the table and successfully commit the data in all versions.
3.     Calling an edit BTF for the same record immediately thereafter, allows me to edit the record and commit the data successfully in 11.1.1.4.0 & 11.1.1.6.0 only. If I perform the same scenario in 11.1.2.1.0 I receive the following exception.
a.     JBO-25003: Object MaintainLocationAM of type ApplicationModule is not found.
4.     Repeating the process, but after editing the first record, edit the second record in the table the error is not encountered. If, after successfully editing the second record and committing the data successfully, I again edit the first record I edited, I receive the same exception as in point 3.
5.     Running any of search BTF’s and calling the edit BTF works in all versions.
For the purpose of having a reusable edit task flow, I need to have the task flow transaction configuration as <Use Existing Transaction if Possible>, shared. This enables me to have the edit task flow as a parent as well as a child task flow and use the task flow functionality irrespective if it is controlling the transaction or not.
My questions are;
1. Is my design acceptable for the solution I am developing, I am more specifically questioning my separation of the AM’s to achieve loosely coupled task flows.
2. Is there a bug (I have done a search on MOS) that details this behaviour.
3. As, in my opinion, this is a common requirement, why is there inconsistency between the versions.
The demo for each version can be made available.
Regards.
Leon.
Edited by: Leon Dorfling on Feb 21, 2013 1:44 AM

Hi Frank,
+1. Its the first sting I stumbled on reading your post. Unless the read-only view object AMs are shared across users (application scope) I don't see why you want to have them in a separate AM. I don't see a benefit in a purely read-only view object that is not backed up by entities and thus would follow Oracle's recommendation to always use entities with view objects.+
The read-only vo's are based on eo's. I separated the AM as the search use cases are independent of one another. So my understanding, from a performance perspective, is to not have all the read-only vo's of the entire hierarchy of products in a single AM if I am only going to access one of them. If I do not understand correctly, can you please assist me in better understanding.
+2. For sure this behavior doesn't sound right and should be filed. You may want to check 11.2.3 in case it has been fixed in there already.+
As posted by Chris, I have through MOS found that it has been fixed in a later version.
Btw.: "Calling an edit BTF for the same record immediately thereafter, allows me to edit the record and commit the data successfully" how do you call this task flow dynamic region or task flow call activity ?
The BTF's are called using a backing bean.
Regards
Leon.

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.4

Koen,
+(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

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

What is the idea behind Render Response and Exception Handling in TF?

Dear All,
While searching for answer for my question, I find it hard to decipher this line.
task flow exception handling doesn't handle any exception that is in Render Response phase
I found this several times in many post like this.
Re: ADF Exception handling (including RENDER RESPNSE PHASE)
and this
Re: Exception Handling in TaskFlow
What's the idea behind exception handling in task flow that is related to JSF/ADF life cycle?
I can't find a resource on why I should know what phase an exception has been thrown?
Sorry if my question might be vague/ignorant to others, but I just would like to know the idea from experts around here. :)
Thanks.
JDEV 11G PS4

Hi,
Render Response is the last lifecycle phase processed during JSF request. The ADF controller has no chance of handling exceptions that occur during this time (example, exception thrown in managed bean) and therefore in its default exception handling implementation ignores this lifecycle phase. As an application developer you don't need to know when an exception is raised. However, if you find that an exception occurs during Render Response and it is not handled by the ADFc declarative exception handler, then you know. You can try and override the framework exception handler as explained here:
https://blogs.oracle.com/jdevotnharvest/entry/extending_the_adf_controller_exception_handler
However, better practice is to use try/catch blocks surrounding e.g. calls in a managed bean that could cause exceptions
Frank

Page flow exception

I have one serious problem when handling exception in page flow. ie.
my code looks like,
// Generated by WebLogic Workshop
// Created on: Mon Dec 01 15:31:45 GMT+05:30 2003
// By: kshashishekar
package portlets.validation.validation;
import com.bea.wlw.netui.pageflow.FormData;
import com.bea.wlw.netui.pageflow.Forward;
import com.bea.wlw.netui.pageflow.PageFlowController;
import com.bea.wlw.netui.tags.html.TreeNode;
import javax.security.auth.login.FailedLoginException;
import javax.servlet.http.HttpServletRequest;
import org.apache.struts.action.ActionErrors;
import org.apache.struts.action.ActionMapping;
import org.apache.struts.action.*;
import com.login.CustomLogin;
import com.bea.p13n.controls.login.UserLoginControl;
* @jpf:controller struts-merge="struts-config-portlets-validation-validation2.xml"
* @jpf:message-resources resources="validation.validator.Message"
* @jpf:view-properties view-properties::
* 
* <view-properties>
* <pageflow-object id="pageflow:/portlets/validation/validation/validationController.jpf"/>
* <pageflow-object id="action:begin.do">
* <property value="280" name="x"/>
* <property value="60" name="y"/>
* </pageflow-object>
* <pageflow-object id="action:validate1.do#portlets.validation.validation.validationController.ValidateForm">
* <property value="220" name="x"/>
* <property value="200" name="y"/>
* </pageflow-object>
* <pageflow-object id="action:logout.do#portlets.validation.validation.validationController.ValidateForm">
* <property value="120" name="x"/>
* <property value="100" name="y"/>
* </pageflow-object>
* <pageflow-object id="action-call:@page:validate1Page1.jsp@#@action:validate1.do#portlets.validation.validation.validationController.ValidateForm@">
* <property value="384,320,320,256" name="elbowsX"/>
* <property value="172,172,192,192" name="elbowsY"/>
* <property value="West_1" name="fromPort"/>
* <property value="East_1" name="toPort"/>
* </pageflow-object>
* <pageflow-object id="page:validate1Page1.jsp">
* <property value="420" name="x"/>
* <property value="180" name="y"/>
* </pageflow-object>
* <pageflow-object id="action-call:@page:Result.jsp@#@action:validate1.do#portlets.validation.validation.validationController.ValidateForm@">
* <property value="156,170,170,184" name="elbowsX"/>
* <property value="332,332,203,203" name="elbowsY"/>
* <property value="East_1" name="fromPort"/>
* <property value="West_2" name="toPort"/>
* </pageflow-object>
* <pageflow-object id="page:Result.jsp">
* <property value="120" name="x"/>
* <property value="340" name="y"/>
* </pageflow-object>
* <pageflow-object id="page:/error.jsp">
* <property value="40" name="x"/>
* <property value="180" name="y"/>
* </pageflow-object>
* <pageflow-object id="forward:path#success#validate1Page1.jsp#@action:begin.do@">
* <property value="316,350,350,384" name="elbowsX"/>
* <property value="52,52,172,172" name="elbowsY"/>
* <property value="East_1" name="fromPort"/>
* <property value="West_1" name="toPort"/>
* <property value="success" name="label"/>
* </pageflow-object>
* <pageflow-object id="forward:path#success#Result.jsp#@action:validate1.do#portlets.validation.validation.validationController.ValidateForm@">
* <property value="184,170,170,156" name="elbowsX"/>
* <property value="192,192,332,332" name="elbowsY"/>
* <property value="West_1" name="fromPort"/>
* <property value="East_1" name="toPort"/>
* <property value="success" name="label"/>
* </pageflow-object>
* <pageflow-object id="forward:path#success#validate1Page1.jsp#@action:logout.do#portlets.validation.validation.validationController.ValidateForm@">
* <property value="156,270,270,384" name="elbowsX"/>
* <property value="92,92,172,172" name="elbowsY"/>
* <property value="East_1" name="fromPort"/>
* <property value="West_1" name="toPort"/>
* <property value="success" name="label"/>
* </pageflow-object>
* <pageflow-object id="control:com.bea.p13n.controls.login.UserLoginControl#myControl">
* <property value="28" name="x"/>
* <property value="34" name="y"/>
* </pageflow-object>
* <pageflow-object id="formbeanprop:portlets.validation.validation.validationController.ValidateForm#username#java.lang.String"/>
* <pageflow-object id="formbeanprop:portlets.validation.validation.validationController.ValidateForm#password#java.lang.String"/>
* <pageflow-object id="formbean:portlets.validation.validation.validationController.ValidateForm"/>
* </view-properties>
public class validationController extends PageFlowController
* This is the control used to generate this pageflow
* @common:control
private UserLoginControl myControl;
// Uncomment this declaration to access Global.app.
// protected global.Global globalApp;
// For an example of page flow exception handling see the example "catch"
and "exception-handler"
// annotations in {project}/WEB-INF/src/global/Global.app
* This method represents the point of entry into the pageflow
* @jpf:action
* @jpf:forward name="success" path="validate1Page1.jsp"
protected Forward begin()
return new Forward( "success" );
* @jpf:action validation-error-page="validate1Page1.jsp"
* @jpf:forward name="success" path="Result.jsp"
* @jpf:catch method="exceptionHandler" type="Exception"
protected Forward validate1(ValidateForm aForm) throws Exception
com.bea.p13n.usermgmt.profile.ProfileWrapper var = myControl.login( aForm.username,
aForm.password, getRequest());
getRequest().setAttribute( "results", var );
return new Forward("success",aForm);
* Action encapsulating the control method :logout
* @jpf:action
* @jpf:forward name="success" path="validate1Page1.jsp"
* @jpf:catch message="not authenticated" path="/error.jsp" type="Exception"
public Forward logout( ValidateForm aForm )
throws Exception
myControl.logout( getRequest() );
return new Forward( "success" );
* @jpf:exception-handler
* @jpf:forward name="errorPage" path="/error.jsp"
protected Forward exceptionHandler( Exception ex, String actionName, String
message, FormData form )
String displayMessage = "An exception occurred in the action " + actionName;
System.out.println ("display message "+displayMessage);
getRequest().setAttribute( "errorMessage", displayMessage );
return new Forward( "errorPage" );
* FormData get and set methods may be overwritten by the Form Bean editor.
public static class ValidateForm extends org.apache.struts.validator.ValidatorForm
private String password;
private String username;
public void setUsername(String username)
this.username = username;
public String getUsername()
return this.username;
public void setPassword(String password)
this.password = password;
public String getPassword()
return this.password;
* added just to test validate (override) method.
public ActionErrors validate(ActionMapping map, HttpServletRequest req)
ActionErrors errors = null;
try {
errors = super.validate(map,req);
}catch (Exception e)
e.printStackTrace();
if (errors ==null) {
System.out.println ("errors = "+errors);
} else
System.out.println ("errors= "+errors);
return errors;
in the above code when we call "validate1" action, it will authenticate successfully
when we enter valid username and passowrd.
But when i enter invalid credentials page flow controller should execute "handleException"
method but at this time i am getting an error
Page Flow Unhandled Exception
Exception: java.lang.IllegalArgumentException
Message: argument type mismatch
A java.lang.IllegalArgumentException exception was thrown and not handled by any
Page Flow. See the console for the exception stack trace.
please help us on how to rectify this error.
thanks,
shashi
[validationController.jpf]

Hi-
That may be on the right track, but the /index.jsp page gets displayed in the
portlet...I am still within the portal framework, so I don't think I am loosing
the context...
-Howie
"Khurram Zafar" <[email protected]> wrote:
>
you are most likely redirecting to the /error.jsp page and losing the
context for
your portal app. The index.jsp page may be defined as your <welcome-file>
in your
web.xml file. The best thing to do is to save the context before visiting
error.jsp
and then provide a link in error.jsp to go back. Look at javadoc for
PageURL for
obtaining the URL to a portal page, you can then save it in session of
pass it
to your error page.
"Howie Oakes" <[email protected]> wrote:
Hello-
I have a page flow portlet that I am testing some exception handling
on. Right
now when I catch an exception, I display the global /error.jsp page,
using the
@jpf:catch tag. The problem is when I refresh the page after viewing
the error
page, the pageflow always pulls up the /index.jsp page at the root of
the webapp.
I have to get a new session to see the original page flow.
This only happens when I am running the Jpf as a portlet...I don't see
this behavior
with it stand-alone.
I am not sure why the index.jsp page is being called...there are noreferences
to it in my jpf code...
thanks,
Howie

Use task flow or simple pages in CRUD?

Hello,
using JDeveloper 12c.
In my case I use task flow to create a simple CRUD, i have two task flow, for it in the first I have a employees table and a button to create a new employee, the button has an action to go to another task flow where I have a Method call of CreateInsert which in turn go a view activity that has a form to create an employee.
The problem is, when committing task makes a return to the main flow but the table not refreshes with the new employee, every task flow isolated handled transactions.
I recommend, work the CRUD with task flow or single pages?
thank you very much in advance.

thank you very much, I got the exact answer, thank you very much again.

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.0

hi,
is there anyone help me out of this issue.

Flow Activity Exception Handling Problem

Hi,
I am using Flow Activity in my Bpel Process, i am getting some exception in one of flow, but other flows are working fine. Even i have included Catch block for other flow still i am getting fault response.
Please suggest me how to do exception handling in Flow Activity.
Thanks in advance.

Hi,
just restructure your BPEL process. The 'Flow' activity contains several 'Sequence' activities. Simply ... put a 'Scope' activity inside of each 'Sequence' activity. Then put another 'Sequence' activity inside of each 'Scope' activity ... and put there required logic/activities.
After that you can create fault handling on these 'Scope' activities. In this way you can handle faults in each flow-sequence.
Regards,
Martin

Unable to pass parameter value from a Task flow to a Portlet

Hi All,
I'm using Jdev 11.1.1.6.0 and created a simple ADF application with one Taskflow which contains one JSF page to display the User details from the default LDAP configured within the Integrated Weblogic Server. The Taskflow have one Parameter to accept the User Email Id as input. Based on the given input value, we will fetch the User details from Weblogic server and display in the JSF Page. I created a portlet out of Taskflow by "Create Portlet Entry" and deployed it onto Integrated Weblogic server.
Portlet works well when executed standalone for the given User Email Id values as input.
Then I created a webcenter Application, On a page, there is a task flow that contains a form with one input text field and one Submit button, and a portlet (that displays the User details from LDAP) that listens for user input from the form. Clicking the Submit button sends the user entered texts to the listening portlet. This is a combination of contextual events established by the producer (task flow) and the wiring of the portlet based parameters from within the consuming page definition file.
The taskflow page which contains the form with Submit button, within the page defintion file contains an event binding (submitEventBinding) and a contextual based event (submitEvent). This event is tied to the ActionListener of the commandButton.
After added both the task flow and the portlet onto a page, I have subscribed to the contextual event of the task flow, and completed the wiring of the Taskflow and Portlet events together.
But in the Form, when I enter the User Email Id in the input filed and click the Submit button, I'm getting the below error -
<LifecycleImpl> <_handleException> ADF_FACES-60098:Faces lifecycle receives unhandled exceptions in phase RESTORE_VIEW 1
java.lang.NullPointerException
     at oracle.portlet.bridge.adf.lifecycle.ADFBridgePhaseListener.afterPhase(ADFBridgePhaseListener.java:74)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:472)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:194)
     at org.apache.myfaces.portlet.faces.bridge.BridgeImpl.doFacesRender(BridgeImpl.java:995)
     at org.apache.myfaces.portlet.faces.bridge.BridgeImpl.doFacesRequest(BridgeImpl.java:903)
     at javax.portlet.faces.GenericFacesPortlet.doBridgeDispatch(GenericFacesPortlet.java:678)
     at javax.portlet.faces.GenericFacesPortlet.doRenderDispatchInternal(GenericFacesPortlet.java:644)
     at javax.portlet.faces.GenericFacesPortlet.doView(GenericFacesPortlet.java:280)
     at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:328)
     at javax.portlet.faces.GenericFacesPortlet.doDispatch(GenericFacesPortlet.java:251)
     at javax.portlet.GenericPortlet.render(GenericPortlet.java:233)
     at oracle.portlet.bridge.adf.application.ADFBridgePortlet.render(ADFBridgePortlet.java:255)
     at com.bea.portlet.container.PortletStub.doRender(PortletStub.java:1012)
     at com.bea.portlet.container.FilterChainGenerator.runFilterChain(FilterChainGenerator.java:127)
     at com.bea.portlet.container.PortletStub.render(PortletStub.java:438)
     at com.bea.portlet.container.AppContainer.renderStub(AppContainer.java:1158)
     at com.bea.portlet.container.AppContainer.invokeRender(AppContainer.java:1090)
     at com.bea.wsrp.producer.adapter.javaportlet.JavaPortletAdapter.doGetMarkup(JavaPortletAdapter.java:294)
     at com.bea.wsrp.producer.handlers.markup.MarkupServiceHandler.doGetMarkup(MarkupServiceHandler.java:449)
     at com.bea.wsrp.producer.handlers.markup.MarkupServiceHandler.doService(MarkupServiceHandler.java:264)
     at com.bea.wsrp.producer.handlers.AbstractServiceHandler.service(AbstractServiceHandler.java:71)
     at com.bea.wsrp.producer.container.ProducerEndPoint.processNow(ProducerEndPoint.java:349)
     at com.bea.wsrp.producer.container.ProducerEndPoint.processNow(ProducerEndPoint.java:250)
     at com.bea.wsrp.producer.container.ProducerEndPoint.processNow(ProducerEndPoint.java:208)
     at oracle.portlet.server.adapter.web.WSRP_v2_Markup_PortTypeSoapToEndpoint.getMarkup(WSRP_v2_Markup_PortTypeSoapToEndpoint.java:74)
     at oasis.names.tc.wsrp.v2.bind.runtime.WSRP_v2_Markup_Binding_SOAP_Tie.invoke_getMarkup(WSRP_v2_Markup_Binding_SOAP_Tie.java:1055)
     at oasis.names.tc.wsrp.v2.bind.runtime.WSRP_v2_Markup_Binding_SOAP_Tie.processingHook(WSRP_v2_Markup_Binding_SOAP_Tie.java:1460)
     at oracle.j2ee.ws.server.StreamingHandler.handle(StreamingHandler.java:299)
     at oracle.j2ee.ws.server.JAXRPCProcessor.doEndpointProcessing(JAXRPCProcessor.java:442)
     at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:1112)
     at oracle.j2ee.ws.server.JAXRPCProcessor.doRequestProcessing(JAXRPCProcessor.java:333)
     at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:233)
     at oracle.j2ee.ws.server.JAXRPCProcessor.doService(JAXRPCProcessor.java:185)
     at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:485)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     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.portlet.producer.container.endpoint.ProducerEndpointFilter.doFilter(ProducerEndpointFilter.java:36)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
     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.wrapRun(WebAppServletContext.java:3715)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
<ProducerLogger> <internalServerError> Internal Server Error:
javax.servlet.ServletException: javax.portlet.PortletException: doBridgeDispatch failed: error from Bridge in executing the request
     at com.bea.portlet.container.PortletStub.render(PortletStub.java:526)
     at com.bea.portlet.container.AppContainer.renderStub(AppContainer.java:1158)
     at com.bea.portlet.container.AppContainer.invokeRender(AppContainer.java:1090)
     at com.bea.wsrp.producer.adapter.javaportlet.JavaPortletAdapter.doGetMarkup(JavaPortletAdapter.java:294)
     at com.bea.wsrp.producer.handlers.markup.MarkupServiceHandler.doGetMarkup(MarkupServiceHandler.java:449)
     at com.bea.wsrp.producer.handlers.markup.MarkupServiceHandler.doService(MarkupServiceHandler.java:264)
     at com.bea.wsrp.producer.handlers.AbstractServiceHandler.service(AbstractServiceHandler.java:71)
     at com.bea.wsrp.producer.container.ProducerEndPoint.processNow(ProducerEndPoint.java:349)
     at com.bea.wsrp.producer.container.ProducerEndPoint.processNow(ProducerEndPoint.java:250)
     at com.bea.wsrp.producer.container.ProducerEndPoint.processNow(ProducerEndPoint.java:208)
     at oracle.portlet.server.adapter.web.WSRP_v2_Markup_PortTypeSoapToEndpoint.getMarkup(WSRP_v2_Markup_PortTypeSoapToEndpoint.java:74)
     at oasis.names.tc.wsrp.v2.bind.runtime.WSRP_v2_Markup_Binding_SOAP_Tie.invoke_getMarkup(WSRP_v2_Markup_Binding_SOAP_Tie.java:1055)
     at oasis.names.tc.wsrp.v2.bind.runtime.WSRP_v2_Markup_Binding_SOAP_Tie.processingHook(WSRP_v2_Markup_Binding_SOAP_Tie.java:1460)
     at oracle.j2ee.ws.server.StreamingHandler.handle(StreamingHandler.java:299)
     at oracle.j2ee.ws.server.JAXRPCProcessor.doEndpointProcessing(JAXRPCProcessor.java:442)
     at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:1112)
     at oracle.j2ee.ws.server.JAXRPCProcessor.doRequestProcessing(JAXRPCProcessor.java:333)
     at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:233)
     at oracle.j2ee.ws.server.JAXRPCProcessor.doService(JAXRPCProcessor.java:185)
     at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:485)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     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.portlet.producer.container.endpoint.ProducerEndpointFilter.doFilter(ProducerEndpointFilter.java:36)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
     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.wrapRun(WebAppServletContext.java:3715)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: javax.portlet.PortletException: doBridgeDispatch failed: error from Bridge in executing the request
     at javax.portlet.faces.GenericFacesPortlet.doBridgeDispatch(GenericFacesPortlet.java:681)
     at javax.portlet.faces.GenericFacesPortlet.doRenderDispatchInternal(GenericFacesPortlet.java:644)
     at javax.portlet.faces.GenericFacesPortlet.doView(GenericFacesPortlet.java:280)
     at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:328)
     at javax.portlet.faces.GenericFacesPortlet.doDispatch(GenericFacesPortlet.java:251)
     at javax.portlet.GenericPortlet.render(GenericPortlet.java:233)
     at oracle.portlet.bridge.adf.application.ADFBridgePortlet.render(ADFBridgePortlet.java:255)
     at com.bea.portlet.container.PortletStub.doRender(PortletStub.java:1012)
     at com.bea.portlet.container.FilterChainGenerator.runFilterChain(FilterChainGenerator.java:127)
     at com.bea.portlet.container.PortletStub.render(PortletStub.java:438)
     ... 57 more
Caused by: javax.portlet.faces.BridgeException: java.lang.NullPointerException
     at org.apache.myfaces.portlet.faces.bridge.BridgeImpl.doFacesRender(BridgeImpl.java:1002)
     at org.apache.myfaces.portlet.faces.bridge.BridgeImpl.doFacesRequest(BridgeImpl.java:903)
     at javax.portlet.faces.GenericFacesPortlet.doBridgeDispatch(GenericFacesPortlet.java:678)
     ... 66 more
Caused by: java.lang.NullPointerException
     at oracle.portlet.bridge.adf.lifecycle.ADFBridgePhaseListener.afterPhase(ADFBridgePhaseListener.java:74)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:472)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:194)
     at org.apache.myfaces.portlet.faces.bridge.BridgeImpl.doFacesRender(BridgeImpl.java:995)
     ... 68 more
*<HTTPClientTransport> <invoke> A request to the producer URL "http://localhost:7101/UserProfilePOC-ViewController-context-root/portlets/WSRP_v2_Markup_Service" resulted in a status 500 response with fault string "Internal Server Error: javax.portlet.PortletException: doBridgeDispatch failed: error from Bridge in executing the request.; nested exception is:*
*     javax.servlet.ServletException: javax.portlet.PortletException: doBridgeDispatch failed: error from Bridge in executing the request". The fault code given was "{urn:oasis:names:tc:wsrp:v2:types}OperationFailed". The producer generated a timestamp of 2012-12-03T14:49:27.557+05:30 and associated the following stack trace with the fault message: com.bea.wsrp.faults.OperationFailedException: Internal Server Error: javax.portlet.PortletException: doBridgeDispatch failed: error from Bridge in executing the request.; nested exception is:*
*     javax.servlet.ServletException: javax.portlet.PortletException: doBridgeDispatch failed: error from Bridge in executing the request*
     at com.bea.wsrp.producer.adapter.javaportlet.JavaPortletAdapter.doGetMarkup(JavaPortletAdapter.java:315)
     at com.bea.wsrp.producer.handlers.markup.MarkupServiceHandler.doGetMarkup(MarkupServiceHandler.java:449)
     at com.bea.wsrp.producer.handlers.markup.MarkupServiceHandler.doService(MarkupServiceHandler.java:264)
     at com.bea.wsrp.producer.handlers.AbstractServiceHandler.service(AbstractServiceHandler.java:71)
     at com.bea.wsrp.producer.container.ProducerEndPoint.processNow(ProducerEndPoint.java:349)
     at com.bea.wsrp.producer.container.ProducerEndPoint.processNow(ProducerEndPoint.java:250)
     at com.bea.wsrp.producer.container.ProducerEndPoint.processNow(ProducerEndPoint.java:208)
     at oracle.portlet.server.adapter.web.WSRP_v2_Markup_PortTypeSoapToEndpoint.getMarkup(WSRP_v2_Markup_PortTypeSoapToEndpoint.java:74)
     at oasis.names.tc.wsrp.v2.bind.runtime.WSRP_v2_Markup_Binding_SOAP_Tie.invoke_getMarkup(WSRP_v2_Markup_Binding_SOAP_Tie.java:1055)
     at oasis.names.tc.wsrp.v2.bind.runtime.WSRP_v2_Markup_Binding_SOAP_Tie.processingHook(WSRP_v2_Markup_Binding_SOAP_Tie.java:1460)
     at oracle.j2ee.ws.server.StreamingHandler.handle(StreamingHandler.java:299)
     at oracle.j2ee.ws.server.JAXRPCProcessor.doEndpointProcessing(JAXRPCProcessor.java:442)
     at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:1112)
     at oracle.j2ee.ws.server.JAXRPCProcessor.doRequestProcessing(JAXRPCProcessor.java:333)
     at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:233)
     at oracle.j2ee.ws.server.JAXRPCProcessor.doService(JAXRPCProcessor.java:185)
     at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:485)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     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.portlet.producer.container.endpoint.ProducerEndpointFilter.doFilter(ProducerEndpointFilter.java:36)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
     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.wrapRun(WebAppServletContext.java:3715)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: javax.servlet.ServletException: javax.portlet.PortletException: doBridgeDispatch failed: error from Bridge in executing the request
     at com.bea.portlet.container.PortletStub.render(PortletStub.java:526)
     at com.bea.portlet.container.AppContainer.renderStub(AppContainer.java:1158)
     at com.bea.portlet.container.AppContainer.invokeRender(AppContainer.java:1090)
     at com.bea.wsrp.producer.adapter.javaportlet.JavaPortletAdapter.doGetMarkup(JavaPortletAdapter.java:294)
     ... 54 more
Caused by: javax.portlet.PortletException: doBridgeDispatch failed: error from Bridge in executing the request
     at javax.portlet.faces.GenericFacesPortlet.doBridgeDispatch(GenericFacesPortlet.java:681)
     at javax.portlet.faces.GenericFacesPortlet.doRenderDispatchInternal(GenericFacesPortlet.java:644)
     at javax.portlet.faces.GenericFacesPortlet.doView(GenericFacesPortlet.java:280)
     at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:328)
     at javax.portlet.faces.GenericFacesPortlet.doDispatch(GenericFacesPortlet.java:251)
     at javax.portlet.GenericPortlet.render(GenericPortlet.java:233)
     at oracle.portlet.bridge.adf.application.ADFBridgePortlet.render(ADFBridgePortlet.java:255)
     at com.bea.portlet.container.PortletStub.doRender(PortletStub.java:1012)
     at com.bea.portlet.container.FilterChainGenerator.runFilterChain(FilterChainGenerator.java:127)
     at com.bea.portlet.container.PortletStub.render(PortletStub.java:438)
     ... 57 more
Caused by: javax.portlet.faces.BridgeException: java.lang.NullPointerException
     at org.apache.myfaces.portlet.faces.bridge.BridgeImpl.doFacesRender(BridgeImpl.java:1002)
     at org.apache.myfaces.portlet.faces.bridge.BridgeImpl.doFacesRequest(BridgeImpl.java:903)
     at javax.portlet.faces.GenericFacesPortlet.doBridgeDispatch(GenericFacesPortlet.java:678)
     ... 66 more
Caused by: java.lang.NullPointerException
     at oracle.portlet.bridge.adf.lifecycle.ADFBridgePhaseListener.afterPhase(ADFBridgePhaseListener.java:74)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:472)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:194)
     at org.apache.myfaces.portlet.faces.bridge.BridgeImpl.doFacesRender(BridgeImpl.java:995)
     ... 68 more
*<PortletRenderer> <setErrorState> An error has occured for Portlet Binding portlet2.*
oracle.portlet.client.container.PortletRemoteException: oracle.portlet.server.container.OperationFailedException: oracle.portlet.wsrp.v2.OperationFailedException: Internal Server Error: javax.portlet.PortletException: doBridgeDispatch failed: error from Bridge in executing the request.; nested exception is:
*     javax.servlet.ServletException: javax.portlet.PortletException: doBridgeDispatch failed: error from Bridge in executing the request*
     at oracle.portlet.client.techimpl.wsrp.WSRPBaseTerminalPipe.processException(WSRPBaseTerminalPipe.java:41)
     at oracle.portlet.client.techimpl.wsrp.WSRPGetMarkupPipe.execute(WSRPGetMarkupPipe.java:267)
     at oracle.portlet.client.techimpl.wsrp.WSRPGetMarkupPipe.pre(WSRPGetMarkupPipe.java:51)
     at oracle.portlet.client.service.pipeline.PipeContext.internalExecute2(PipeContext.java:650)
     at oracle.portlet.client.service.pipeline.PipeContext.access$000(PipeContext.java:48)
     at oracle.portlet.client.service.pipeline.PipeContext$1.run(PipeContext.java:498)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
     at oracle.security.jps.internal.jaas.AccActionExecutor.execute(AccActionExecutor.java:74)
     at oracle.security.jps.internal.jaas.CascadeActionExecutor$SubjectPrivilegedExceptionAction.run(CascadeActionExecutor.java:83)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.security.Security.runAs(Security.java:61)
     at oracle.security.jps.wls.jaas.WlsActionExecutor.execute(WlsActionExecutor.java:51)
     at oracle.security.jps.internal.jaas.CascadeActionExecutor.execute(CascadeActionExecutor.java:56)
     at oracle.security.jps.internal.jaas.AbstractSubjectSecurity.executeAs(AbstractSubjectSecurity.java:138)
     at oracle.portlet.client.service.pipeline.PipeContext.internalExecute(PipeContext.java:502)
     at oracle.portlet.client.service.pipeline.PipeContextRunnable.run(PipeContextRunnable.java:23)
     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
     at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
     at java.util.concurrent.FutureTask.run(FutureTask.java:138)
     at oracle.portlet.client.service.pipeline.ModifiedThreadPoolExecutor$Worker.runTask(ModifiedThreadPoolExecutor.java:391)
     at oracle.portlet.client.service.pipeline.ModifiedThreadPoolExecutor$Worker.run(ModifiedThreadPoolExecutor.java:416)
     at java.lang.Thread.run(Thread.java:662)
Caused by: oracle.portlet.server.container.OperationFailedException: oracle.portlet.wsrp.v2.OperationFailedException: Internal Server Error: javax.portlet.PortletException: doBridgeDispatch failed: error from Bridge in executing the request.; nested exception is:
     javax.servlet.ServletException: javax.portlet.PortletException: doBridgeDispatch failed: error from Bridge in executing the request
     at oracle.portlet.wsrp.v2.ServerToWSRPv2.getMarkup(ServerToWSRPv2.java:6703)
     at oracle.portlet.client.connection.wsrp.ActivityServerWrapper.getMarkup(ActivityServerWrapper.java:1812)
     at oracle.portlet.client.techimpl.wsrp.WSRPGetMarkupPipe.execute(WSRPGetMarkupPipe.java:135)
     ... 22 more
Caused by: oracle.portlet.wsrp.v2.OperationFailedException: Internal Server Error: javax.portlet.PortletException: doBridgeDispatch failed: error from Bridge in executing the request.; nested exception is:
     javax.servlet.ServletException: javax.portlet.PortletException: doBridgeDispatch failed: error from Bridge in executing the request
     at oracle.portlet.wsrp.v2.WSRP_v2_Markup_PortTypeJaxbToSoap.getMarkup(WSRP_v2_Markup_PortTypeJaxbToSoap.java:136)
     at oracle.portlet.wsrp.v2.ServerToWSRPv2.getMarkup(ServerToWSRPv2.java:6535)
     ... 24 more
Caused by: oracle.portlet.wsrp.v2.soap.OperationFailed
     at oracle.portlet.wsrp.v2.soap.runtime.WSRP_v2_Markup_PortType_getMarkup_Fault_SOAPSerializer.deserializeDetail(WSRP_v2_Markup_PortType_getMarkup_Fault_SOAPSerializer.java:299)
     at oracle.j2ee.ws.common.encoding.SOAPFaultInfoSerializer.doDeserializeSOAP11(SOAPFaultInfoSerializer.java:133)
     at oracle.j2ee.ws.common.encoding.SOAPFaultInfoSerializer.doDeserialize(SOAPFaultInfoSerializer.java:95)
     at oracle.j2ee.ws.common.encoding.ObjectSerializerBase.deserialize(ObjectSerializerBase.java:194)
     at oracle.j2ee.ws.common.encoding.ReferenceableSerializerImpl.deserialize(ReferenceableSerializerImpl.java:148)
     at oracle.portlet.wsrp.v2.soap.runtime.WSRP_v2_Markup_Binding_SOAP_Stub._readBodyFaultElement(WSRP_v2_Markup_Binding_SOAP_Stub.java:723)
     at oracle.j2ee.ws.client.StreamingSender._sendImpl(StreamingSender.java:396)
     at oracle.j2ee.ws.client.StreamingSender._send(StreamingSender.java:148)
     at oracle.portlet.wsrp.v2.soap.runtime.WSRP_v2_Markup_Binding_SOAP_Stub.getMarkup(WSRP_v2_Markup_Binding_SOAP_Stub.java:341)
     at oracle.portlet.wsrp.v2.WSRP_v2_Markup_PortTypeJaxbToSoap.getMarkup(WSRP_v2_Markup_PortTypeJaxbToSoap.java:86)
     ... 25 more
Please help me to resolve this error and let me know if you need any more details.
Regards,
Udaya

Here is the solution
<spartacus:taskDetails row="#{row}" submissionId="#{row.bindings.SubmissionId.inputValue}" >

<f:facet name="loadMSPageLink">
<af:commandLink id="cl29" text="#{row.bindings.FullTitle.inputValue}"
styleClass="home-title"
actionListener="#{pageFlowScope.homepagebean.navigateToMSLandingPage}">
<f:attribute name="submissionId"
value="#{row.bindings.SubmissionId.inputValue}"/>
</af:commandLink>
</f:facet>

<f:facet name="loadUserProfile">
<af:commandLink id="cl10" text="#{row.bindings.EditorName.inputValue}" actionListener="#{pageFlowScope.homepagebean.loadUserProfile}" styleClass="link-class">
<f:attribute name="editorName"
value="#{row.bindings.EditorName.inputValue}"/>
</af:commandLink>
</f:facet>
</spartacus:taskDetails>
<af:spacer height="5px" id="s39"/>
     <af:facetRef facetName="loadMSPageLink"/>
     <af:spacer height="5px" id="s40"/>
     <af:panelGroupLayout id="pgl57" layout="horizontal">
     <af:outputText value="#{viewcontrollerBundle.EDITOR}" id="ot37" styleClass="strong-style"/>
     <af:spacer width="2px" id="s41"/>
     <af:facetRef facetName="loadUserProfile"/>
     <af:spacer width="2px" id="s42"/>

JDev 11.1.2.4.0 Can't Open Unbounded Task Flow

I just created a new Fusion application. When I click on the unbounded task flow adfc-config.xml I get an error dialog box An unexpected severe error has occured in JDeveloper.
It seems that same issue as in that discussion https://forums.oracle.com/thread/2565042?start=0&tstart=0 except that I am not using mobile extension. I can't downgrade JDev to JDK 1.6. I use 1.7.0_25. Any workaround?
Stack Trace:
Failed to create an instance of editor oracle.adfdt.controller.adfc.diagram.editor.AdfcDiagramEditor
java.lang.reflect.InvocationTargetException
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
j.lang.reflect.Constructor.newInstance(Constructor.java:526)
o.ii.editor.EditorState.createEditor(EditorState.java:154)
o.ii.editor.EditorState.getOrCreateEditor(EditorState.java:102)
o.ii.editor.SplitPaneState.canSetEditorStatePos(SplitPaneState.java:251)
o.ii.editor.SplitPaneState.setCurrentEditorStatePos(SplitPaneState.java:214)
o.ii.editor.TabGroupState.createSplitPaneState(TabGroupState.java:105)
o.ii.editor.TabGroup.addTabGroupState(TabGroup.java:394)
o.ii.editor.EditorManagerImpl.createEditor(EditorManagerImpl.java:786)
o.ii.editor.EditorManagerImpl.createEditor(EditorManagerImpl.java:720)
o.ii.editor.EditorManagerImpl.openEditor(EditorManagerImpl.java:637)
o.ii.navigator.OpenEditorController.whenOpenEditor(OpenEditorController.java:41)
o.ii.navigator.OpenEditorContextMenuListener.handleDefaultAction(OpenEditorContextMenuListener.java:51)
o.i.controller.ContextMenuListenersHook$LazyContextMenuListener.handleDefaultAction(ContextMenuListenersHook.java:219)
o.i.controller.ContextMenu.fireDefaultAction(ContextMenu.java:447)
o.ii.explorer.BaseTreeExplorer.fireDefaultAction(BaseTreeExplorer.java:1900)
o.ii.explorer.BaseTreeExplorer.dblClicked(BaseTreeExplorer.java:2249)
o.ii.explorer.BaseTreeExplorer.mouseReleased(BaseTreeExplorer.java:2278)
o.ii.explorer.CustomTree.processMouseEvent(CustomTree.java:211)
j.a.Component.processEvent(Component.java:6270)
j.a.Container.processEvent(Container.java:2229)
j.a.Component.dispatchEventImpl(Component.java:4861)
j.a.Container.dispatchEventImpl(Container.java:2287)
j.a.Component.dispatchEvent(Component.java:4687)
j.a.LightweightDispatcher.retargetMouseEvent(Container.java:4832)
j.a.LightweightDispatcher.processMouseEvent(Container.java:4492)
j.a.LightweightDispatcher.dispatchEvent(Container.java:4422)
j.a.Container.dispatchEventImpl(Container.java:2273)
j.a.Window.dispatchEventImpl(Window.java:2719)
j.a.Component.dispatchEvent(Component.java:4687)
j.a.EventQueue.dispatchEventImpl(EventQueue.java:735)
j.a.EventQueue.access$200(EventQueue.java:103)
j.a.EventQueue$3.run(EventQueue.java:694)
j.a.EventQueue$3.run(EventQueue.java:692)
j.security.AccessController.doPrivileged(Native Method)
j.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
j.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:87)
j.a.EventQueue$4.run(EventQueue.java:708)
j.a.EventQueue$4.run(EventQueue.java:706)
j.security.AccessController.doPrivileged(Native Method)
j.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
j.a.EventQueue.dispatchEvent(EventQueue.java:705)
o.javatools.internal.ui.EventQueueWrapper._dispatchEvent(EventQueueWrapper.java:169)
o.javatools.internal.ui.EventQueueWrapper.dispatchEvent(EventQueueWrapper.java:151)
j.a.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242)
j.a.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161)
j.a.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
j.a.EventDispatchThread.pumpEvents(EventDispatchThread.java:146)
j.a.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)
j.a.EventDispatchThread.run(EventDispatchThread.java:91)
Caused by:
java.lang.NoClassDefFoundError: Could not initialize class oracle.diagram.framework.action.Actions
o.diagram.framework.action.handler.ZoomInHandler.<clinit>(ZoomInHandler.java:22)
o.diagram.framework.editor.CommonDiagram.<clinit>(CommonDiagram.java:100)
o.adfdt.controller.adfc.diagram.editor.AdfcDiagramEditor.<init>(AdfcDiagramEditor.java:17)
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
j.lang.reflect.Constructor.newInstance(Constructor.java:526)
o.ii.editor.EditorState.createEditor(EditorState.java:154)
o.ii.editor.EditorState.getOrCreateEditor(EditorState.java:102)
o.ii.editor.SplitPaneState.canSetEditorStatePos(SplitPaneState.java:251)
o.ii.editor.SplitPaneState.setCurrentEditorStatePos(SplitPaneState.java:214)
o.ii.editor.TabGroupState.createSplitPaneState(TabGroupState.java:105)
o.ii.editor.TabGroup.addTabGroupState(TabGroup.java:394)
o.ii.editor.EditorManagerImpl.createEditor(EditorManagerImpl.java:786)
o.ii.editor.EditorManagerImpl.createEditor(EditorManagerImpl.java:720)
o.ii.editor.EditorManagerImpl.openEditor(EditorManagerImpl.java:637)
o.ii.navigator.OpenEditorController.whenOpenEditor(OpenEditorController.java:41)
o.ii.navigator.OpenEditorContextMenuListener.handleDefaultAction(OpenEditorContextMenuListener.java:51)
o.i.controller.ContextMenuListenersHook$LazyContextMenuListener.handleDefaultAction(ContextMenuListenersHook.java:219)
o.i.controller.ContextMenu.fireDefaultAction(ContextMenu.java:447)
o.ii.explorer.BaseTreeExplorer.fireDefaultAction(BaseTreeExplorer.java:1900)
o.ii.explorer.BaseTreeExplorer.dblClicked(BaseTreeExplorer.java:2249)
o.ii.explorer.BaseTreeExplorer.mouseReleased(BaseTreeExplorer.java:2278)
o.ii.explorer.CustomTree.processMouseEvent(CustomTree.java:211)
j.a.Component.processEvent(Component.java:6270)
j.a.Container.processEvent(Container.java:2229)
j.a.Component.dispatchEventImpl(Component.java:4861)
j.a.Container.dispatchEventImpl(Container.java:2287)
j.a.Component.dispatchEvent(Component.java:4687)
j.a.LightweightDispatcher.retargetMouseEvent(Container.java:4832)
j.a.LightweightDispatcher.processMouseEvent(Container.java:4492)
j.a.LightweightDispatcher.dispatchEvent(Container.java:4422)
j.a.Container.dispatchEventImpl(Container.java:2273)
j.a.Window.dispatchEventImpl(Window.java:2719)
j.a.Component.dispatchEvent(Component.java:4687)
j.a.EventQueue.dispatchEventImpl(EventQueue.java:735)
j.a.EventQueue.access$200(EventQueue.java:103)
j.a.EventQueue$3.run(EventQueue.java:694)
j.a.EventQueue$3.run(EventQueue.java:692)
j.security.AccessController.doPrivileged(Native Method)
j.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
j.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:87)
j.a.EventQueue$4.run(EventQueue.java:708)
j.a.EventQueue$4.run(EventQueue.java:706)
j.security.AccessController.doPrivileged(Native Method)
j.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
j.a.EventQueue.dispatchEvent(EventQueue.java:705)
o.javatools.internal.ui.EventQueueWrapper._dispatchEvent(EventQueueWrapper.java:169)
o.javatools.internal.ui.EventQueueWrapper.dispatchEvent(EventQueueWrapper.java:151)
j.a.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242)
j.a.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161)
j.a.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
j.a.EventDispatchThread.pumpEvents(EventDispatchThread.java:146)
j.a.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)
j.a.EventDispatchThread.run(EventDispatchThread.java:91)

No, there is no workaround for this. You can open a SR and let Oracle work on this. We can't do anything about it.
Why can't you install jdk 1.6?
You can have more then one jdk installed on your pc.
You can use in jdk which comes with the installation package,
Timo

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
Switzerland

The 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

Global Exception Handling

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
Zmeda

refer 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

Task flow exception handler

Similar Messages

Maybe you are looking for