new features in beta

[hoffa]

is there something I have to follow, when I want to make use of the new exceptions.xml? I'd like a catch-all like it's described in the docs. So I just put

<exceptions>
 <exception>
 <redirect view-id="/failure.xhtml">Unexpected failure</redirect>
 <end-conversation/>
 </exception>
</exceptions>

in the exception.xml. And to test it I put inside an action-method

if (true)
 throw new NullPointerException("exception test");

but still I see the seam debug page.

Another new feature I'm trying to figure out is the no-conversation-view-id for nodes. I understand that it is now possible to do something like:

<page view-id="/members/*" no-conversation-view-id="/members/main.xhtml"/>

,right? But how?

[gavin.king]

Do you have the SeamExceptionFilter installed?

[iradix]

It's not possible to use a no-conversation-view-id on a wildcard just yet. I'm hoping to submit a patch for that today.

[hoffa]

@iradix: thank you. that's great!

@gavin: yes I do. Like this in web.xml:

 <filter>
 <filter-name>Seam Exception Filter</filter-name>
 <filter-class>org.jboss.seam.servlet.SeamExceptionFilter</filter-class>
 </filter>

 <filter-mapping>
 <filter-name>Seam Exception Filter</filter-name>
 <url-pattern>*.jsf</url-pattern>
 </filter-mapping>

[gavin.king]

but still I see the seam debug page.

I just checked the code. The debug page takes priority over the catch-all. So just disable the debug page.

[hoffa]

that's it, thanks! just a note: the docs(topic 1.6.5.) are a bit wrong here: org.jboss.seam.core.init.debug has to be set explicitly to false.

is it possible to access the exception somehow, in order to send a stack trace along with the page, the error occured on, per email to an admin?