Exception Handling In Struts, Declarative, programatic and customized excep

hello .
I'm workingon exception handling in struts , i executed the gobal exceptions.
In glabal exception handling , one will not get the root cause of exception , rather we print the message from resource bundle.
How to get the root cause of exception in jsp page.
Give me sample code to deal with ExceptionHandler claas.
Thank u
Roshu

Hi ,
I am in the same situation. Global exception is working fine in my struts application . But I need to show the exception stack trace also in the screen whenever the exception occurs.Can anyone please provide me a sample code to deal with ExceptionHandler class ?
Thanks in advance...
Regards,
BG

Similar Messages

Exception Handling for OPEN DATA SET and CLOSE DATA SET

Hi ppl,
Can you please let me know what are the exceptions that can be handled for open, read, transfer and close data set ?
Many Thanks.

HI,
try this way....
DO.
    TRY.
    READ DATASET filename INTO datatab.
      CATCH cx_sy_conversion_codepage cx_sy_codepage_converter_init
            cx_sy_file_authority cx_sy_file_io cx_sy_file_open .
    ENDTRY.
READ DATASET filename INTO datatab.
End of changes CHRK941728
    IF sy-subrc NE 0.
      EXIT.
    ELSE.
      APPEND datatab.
    ENDIF.
ENDDO.

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

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

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

GP Exception handling doesn't work

I had implemented the GP Exception handling scenario described in [Configuring Exception Handling|http://help.sap.com/saphelp_nw2004s/helpdata/en/44/10bd4029450d1be10000000a114a6b/frameset.htm].
But when I start the process and input a wrong user id, the exception handling action doesn't start and the process keep in running status. When I check the Background Action Processor Queue, the queue entry of action "Retrieve User Details" retry executing continously.
And when I check the background callable object, it report that "Obsolete process exception: E_NO_USER_FOUND " in section Process Exceptions Check .
Is it a system bug or Is something wrong in system configuration?
BTW: The environment is NW7.0 SP13 Java Stack

Reposting

Exception Handling Confusion!

I require the following very basic functionality from a function.
Create or Replace function fnc_get_col3 (a in number, b in number)
return number
as
begin
return select col3 from TAB1 where col1 = a and col2 = b;
end fnc_get_util;
My question is that can I use the regular exception handling (like 'No data found' and 'Too many rows') in above function when i am using the return and select statement in same line
OR do i have to recreate this function as
Create or Replace function fnc_get_col3 (a in number, b in number)
return number
as
abc number(5);
begin
select col3 into abc from TAB1 where col1 = a and col2 = b;
return abc;
exception
when no data found then
dbms_ouput.put_line 'No data found'
end fnc_get_util;
Thanks in Advance

Why do you believe it is syntactically valid to return a value this way? The first function does not compile and cannot compile so there is no exception handling to discuss
SQL> create or replace function f1
2    return number
3 is
4 begin
5    return select count(*) from emp;
6 end;
7 /
Warning: Function created with compilation errors.
SQL> sho err
Errors for FUNCTION F1:
LINE/COL ERROR
5/10     PLS-00103: Encountered the symbol "SELECT" when expecting one of
         the following:
         ( - + ; case mod new not null <an identifier>
         <a double-quoted delimited-identifier> <a bind variable>
         continue avg count current exists max min prior sql stddev
         sum variance execute forall merge time timestamp interval
         date <a string literal with character set specification>
         <a number> <a single-quoted SQL string> pipe
         <an alternatively-quoted string literal with character set
         specification>
         <an alternYou would need your SELECT statement to select data into a local variable and to return that local variable as you are doing in your second implementation. It would not make sense, however, to have an exception handler that simply uses DBMS_OUTPUT to display a message-- you should only catch an exception if you can do something meaningful with it.
Justin

Study security related exception handling in Java

Hi all,
I am required to do an indepth study on security-related exception handling in Java, their Pluses and minuses... Can ppl suggest me places where I can get a kick start? Any resource that u know can help me out?
I appreciate ur help in this regard...FYI, I am a grad student and I am doing this as a part of my course-work...I am writing up a report on this...
Thanx a bunch, in advance for ur help ppl..

Take a look at the JAAS API and docs.
- Saish

Webservices and custom exception handling

hi all,
I have one ejb method which promote as webservices.
@WebMethod
@Oneway
public void test(String arg) throws STARS21BOException{
my Custom Exception class STARS21BOException extends from EjbException and it has no-arg constructor.
but when i deploy on server i get following exception.
if i remove throws clause from method, it is working fine.
javax.xml.ws.WebServiceException: Unable to create JAXBContext
     at com.sun.xml.ws.model.AbstractSEIModelImpl.createJAXBContext(AbstractSEIModelImpl.java:158)
     at com.sun.xml.ws.model.AbstractSEIModelImpl.postProcess(AbstractSEIModelImpl.java:87)
     at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:271)
     at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:351)
     at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:201)
     Truncated. see log file for complete stacktrace
Caused By: java.security.PrivilegedActionException: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts of IllegalAnnotationExceptions
java.lang.StackTraceElement does not have a no-arg default constructor.
     this problem is related to the following location:
          at java.lang.StackTraceElement
          at public java.lang.StackTraceElement[] java.lang.Throwable.getStackTrace()
          at java.lang.Throwable
          at java.lang.Exception
          at public java.lang.Exception sg.com.stee.stars21.showcase.business.jaxws.STARS21BOExceptionBean.causedByException
          at sg.com.stee.stars21.showcase.business.jaxws.STARS21BOExceptionBean
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sun.xml.ws.model.AbstractSEIModelImpl.createJAXBContext(AbstractSEIModelImpl.java:148)
     at com.sun.xml.ws.model.AbstractSEIModelImpl.postProcess(AbstractSEIModelImpl.java:87)
     at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:271)
     at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:351)
     Truncated. see log file for complete stacktrace
Caused By: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts of IllegalAnnotationExceptions
java.lang.StackTraceElement does not have a no-arg default constructor.
     this problem is related to the following location:
          at java.lang.StackTraceElement
          at public java.lang.StackTraceElement[] java.lang.Throwable.getStackTrace()
          at java.lang.Throwable
          at java.lang.Exception
          at public java.lang.Exception sg.com.stee.stars21.showcase.business.jaxws.STARS21BOExceptionBean.causedByException
          at sg.com.stee.stars21.showcase.business.jaxws.STARS21BOExceptionBean
     at com.sun.xml.bind.v2.runtime.IllegalAnnotationsException$Builder.check(IllegalAnnotationsException.java:102)
     at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:438)
     at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:286)
     at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139)
     at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:105)
     Truncated. see log file for complete stacktrace
>
<Apr 23, 2010 10:51:33 AM SGT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1271991082383' for task '2'. Error is: 'weblogic.application.ModuleException: Exception activating module: EJBModule(ejb-showcaseEJB.jar)

newt.mm wrote:
@WebMethod
@Oneway
public void test(String arg) throws STARS21BOException{
}As per method signature it is asynchronous web service however you are trying to throw soap fault. Isn't the soap fault is also a kind of response?
Do you really want your web method to be asynchronous?

Struts exception handling - Exception handler

Hi ,
I need some help for struts exception handling . Global exception is working fine in my struts application . But I need to show the exception stack trace also in the screen whenever the exception occurs.I guess this can be achieved if we use a custom exception handler instead of struts default exception handler . Can anyone please provide me a sample code to deal with a custom ExceptionHandler class ?
Thanks in advance...
Regards,
BG

The struts provides org.apache.struts.action.ExceptionHandler class for creating the custom exception handlers. All the custom Exception Handlers should extend the ExceptionHandler class and override the execute() method.
//An Example
import javax.servlet.ServletException;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import org.apache.struts.action.ActionForm;
import org.apache.struts.action.ActionForward;
import org.apache.struts.action.ActionMapping;
import org.apache.struts.action.ExceptionHandler;
import org.apache.struts.config.ExceptionConfig;
public class CustomExceptionHandler extends ExceptionHandler {
public ActionForward execute(Exception exception, ExceptionConfig config, ActionMapping mapping, ActionForm formInstance,
HttpServletRequest request, HttpServletResponse response) throws ServletException {
try {
// TODO CustomeCode
System.out.println("Exception Handler for the specific error");
}catch (Exception e) {
return (super.execute(exception, config, mapping, formInstance, request, response));
Struts-config.xml File
<exception key="error.system" type="java.lang.RuntimeException"
handler="com.visualbuilder.handler.CustomExceptionHandler" path="/index.jsp" />
Note:- This will transfer the control to the index.jsp after calling the exception handler. In the struts-config.xml we are adding the global exception for RuntimeException. You can add any exception like the previous example to some actions only.
I have taken this example from following link. You may visit it.
http://www.visualbuilder.com/jsp/struts/tutorial/pageorder/38/
I would like if you share knowledge with me.

Exception with the type CX_SY_OPEN_SQL_DB occured and was not handled

Hi Champs,
I am working on an interface which picks up file uploaded in a XI server and process it. The Function module used is a Z function module, developed locally.
I am uploading an tab limited file in XI server and a background job processes the file. The tab limited file contains Payelement Transaction ID as primary key. And after validation of elements like WBS element, cost center etc the file is posted using BAPI BAPI_ACC_DOCUMENT_POST. And all the Payelement Trans Ids are also replicated in a Z table, with there status viz. Success or Error or Warning.
After background job was completed, we found in Tcode SXMB_MONI that the file was in error.
The error message was :
Error during proxy processing An exception with the type CX_SY_OPEN_SQL_DB occurred, but was neither handled locally, nor declared in a RAISING clause The system tried to insert a data record, even though a data record with the same primary key already exists.
But to my dismay, I found that some of the Payelement Trans Ids were posted for a document and are also replicated in my Z table.
From the error it seems that we are inserting a record that is already there in the document. I have checked in for BAPI's input parameter, there is nothing duplicate.
Note: Insertion in Z table is made after the BAPI BAPI_ACC_DOCUMENT_POST.
Can you help me out in this issue as it is now getting into veins
Reagrds,
Nishant

Hi,
Even we have faced this kind of issue. In order to solve this just write the following code:
1) Before inserting records in to Z table, write one select query on that table with primary key fields in where clause. Pass the value that are returned by BAPI BAPI_ACC_DOCUMENT_POST to the key field.
2) If sy-subrc = 4, insert records in Z table else Continue and dont insert records in this table.
This will solve your problem.
Regards,
Prashant

Exception Handling Standards -The exception Exception should never been thrown. Always Subclass Exception and throw the subclassed Classes.

In the current project my exception handling implementation is as follows :
Exception Handling Layer wise :
DL layer :
catch (Exception ex)
bool rethrow = ExceptionPolicy.HandleException(ex, "Ui Policy");
if (rethrow)
throw;
BL Layer
catch (Exception ex)
bool rethrow = ExceptionPolicy.HandleException(ex, "Ui Policy");
if (rethrow)
throw;
UI Layer
catch (Exception ex)
bool rethrow = ExceptionPolicy.HandleException(ex, "Ui Policy");
if (rethrow)
Response.Redirect("ErrorPage.aspx", false);
We have a tool to check the standards. And tool output is as follows :
The exception Exception should never been thrown. Always Subclass Exception and throw the subclassed Classes.
I need suggestions on how to implement the same according to standards.

Your tool is wrong if it says to never throw Exception. This was a common recommendation back in the .NET v1 days but has long since been thrown out. It is perfectly fine to use Exception when you have a general exception that provides no information
that an application can use to make an informed opinion.
The general rules of exception throwing is to throw the most specific exception that makes sense. If there is no specific exception that applies and it would be useful for the caller to handle the exception differently than other exceptions then creating
a custom exception type is warranted. Otherwise throwing Exception is reasonable. As an example you might have an application that pulls back product data given an ID. There is no built in exception that says the ID is invalid. However an invalid ID
is something that an application may want to handle differently than, say, an exception about the product being discontinued. Therefore it might make sense to create an ItemNotFoundException exception that the application can react to.
Conversely there is no benefit in having different exception types for disk full and disk quota met. The application will respond the same in either case.
Michael Taylor
http://blogs.msmvps.com/p3net

Exception handling in Custom Login procedure

Hi,
I have a custom login procedure. Now instead of handling the possible exceptions in a custom way too, I want to use the syntax of the exception handling API (probably the one in the PDK) the default login procedure uses. Can someone point me to the values the default login procedure uses?
Thanks, Tony

Tony,
The default login page (the source of which is now unwrapped in 3.0.0), uses the following snippet of code to report the errors:
if p_error then
wwerr_api_error_ui.show_inline_html;
end if;The errors are stacked when the ls_login procedure is executed, and the next time the login page is called up, it just displays the stacked errors.

Custom code as an exception handler not working.

Hi,
I worked on Custom Handler for unauthorized access to a taskflow following the link below and it worked. But a special case in this doesn't work.
http://download.oracle.com/docs/cd/E14571_01/web.1111/b31974/taskflows_complex.htm#ADFFD22602
Scenario-1: I have a link that opens an unauthorized taskflow as blank page. I tried the solution of custom handler and am able to display message or display error page --- WORKS FINE
Scenario-2: I have a link that opens an unauthorized taskflow in a pop-up as blank page. The above solution doesn't work. I tried displaying SOPs but nothing gets print --- DOESN'T WORK.
Details:
The custom handler doesn't work with Pop-ups. I have an unauthorized taskflow that gets called inside a pop-up using a link. Being an unauthorized user, I click on the link and it pops-up with a blank page. As per the custom handler it is supposed to display error-page. But it doesn't.
I tried displaying SOPs inside the handleException method and nothing prints. The exception handler is unable to catch the exception. If this use-case throws some exception, my exception handler would have handle it but it doesn't raise any exception.
Is this something issue that I need to discuss with FMW team?
Any workaround for this would be of great help.
Code Sample:
public void handleException(FacesContext facesContext, Throwable throwable,
PhaseId phaseId) throws Throwable {
String errorMessage = throwable.getMessage();
if (errorMessage != null && errorMessage.indexOf("ADFC-0619") > -1) {
setEL("#{sessionScope.errorMessage}",
"You are not authorized to view this page.");
ExternalContext externalContext =
facesContext.getExternalContext();
externalContext.redirect("ErrorPage");
} else {
super.handleException(facesContext, throwable, phaseId);
Thanks
Raza

Hi Frank,
This scenario is not specific to a particular TaskFlow. In General, there are links in some views, that invokes taskflows and a particular user may not have permission to that TaskFlow. In this scenario, I am not sure where I need to define the method or router. And Hence I registered the Custom Exception Handler as a service as per the documentation.
But the logic in documentation doesn't work with Pop-ups.
Thanks
Raza

Handling runtime Exceptions in tomcat / struts

Hi, I'm trying to find a way to cleanly handle exceptions in struts/tomcat. I've read a number of suggestions in my struts book, but none seem to work.
What I've done is created an instance within my action class that deliberatley creates a NullPointerException. I want to be able to display an errorPage at this point, but whatever I do I just get the same horrible HTTP Status 500 error.
Can anyone give any advice with this please?

Check out the org.apache.struts.action.ExceptionHandler class. Basically you extend this class, and override the execute method. In the struts config file you add this entry...
<global-exceptions>
<exception
handler="the pathname of the class that extends ExceptionHandler"
key="message properties entry"
path="error page jsp"
scope="request"
type="type of Exception you want to catch (Throwable)"/>
</global-exceptions>
This basically acts as a "catch all" global exception handle.

Exception Handling In Struts, Declarative, programatic and customized excep

Similar Messages

Maybe you are looking for