-
1. Re: handleException details
nickarls Feb 1, 2008 8:40 AM (in response to saasira)The exception should be available in org.jboss.seam.handledException, you should be able to get the full stack trace from there.
-
2. Re: handleException details
nickarls Feb 1, 2008 8:43 AM (in response to saasira)Meaning that you should be able to forward to a page that uses a bean that injects the exception and then generates a String from the stacktrace.
-
3. Re: handleException details
saasira Feb 1, 2008 1:05 PM (in response to saasira)How it injects the exception? Could you please give some example.
I have something like this
<end-conversation/>
<redirect view-id="/error.seam">
Unexpected error: #{org.jboss.seam.handledException.getMessage()} -
4. Re: handleException details
pmuir Feb 3, 2008 5:50 PM (in response to saasira)@In Exception handledException;
-
5. Re: handleException details
saasira Feb 3, 2008 11:20 PM (in response to saasira)Hi,
@In is throwing exception as below
ExceptionFilt E org.jboss.seam.web.ExceptionFilter doFilter exception root cause
org.jboss.seam.RequiredException: @In attribute requires non-null value: errorbean.handledException -
6. Re: handleException details
nickarls Feb 4, 2008 1:45 AM (in response to saasira)Then make in non-required. Depending on the scope and how/where the bean is referenced, it might be created even when there was no error...
-
7. Re: handleException details
saasira Feb 4, 2008 4:18 AM (in response to saasira)Exception that I injected was null.
But I could get that exception as
Exception excp= (Exception)Contexts.getConversationContext().get("org.jboss.seam.handledException");
if (excp != null && excp instanceof Exception) {
System.out.println("error" + excp.getClass().getName());
excp.printStackTrace();
but printStacjTrace doesnt print anything now. But esxception class name is proper.