-
1. Re: Exceptions in page param converters
adamw Oct 25, 2007 3:16 AM (in response to adamw)But then, in the converter I have
@In private EntityManager entityManager
which is conversation-scoped, so the context must be created by then :). And it should last until the response is rendered, right? -
2. Re: Exceptions in page param converters
pmuir Oct 25, 2007 11:57 AM (in response to adamw)Yes, it should display the message - the conversation is there inside the PROCESS VALIDATORS phase. You'll have to debug, or file a testcase in jira.
Btw ConverterException should normally be handled as faces messages - you need to mark the converter @BypassInterceptors for them to be passed through unwrapped and so rendered as faces messages. -
3. Re: Exceptions in page param converters
igx89 Oct 25, 2007 12:46 PM (in response to adamw)It could be related to this issue: http://jira.jboss.com/jira/browse/JBSEAM-2139. There's been a lot of reports recently about messages not propagating to error pages.
-
4. Re: Exceptions in page param converters
adamw Oct 25, 2007 4:34 PM (in response to adamw)It probably is related to this issue :).
However, I didn't have @BypassInterceptors, so that I could have some values injected (I had @In EntityManager entityManager). Now that I removed it, I have to lookup the entity manager manually. But how can I do that?
Writing:EntityManager entityManager = (EntityManager) Contexts.lookupInStatefulContexts("entityManager");
in the method returns null. And the @In version worked, except for the message.
Thanks,
Adam -
5. Re: Exceptions in page param converters
adamw Oct 26, 2007 8:34 AM (in response to adamw)Ok, found it, Component.getInstance() :)
Thought, even after removing @BypassInterceptors from the converter, the message isn't shown on the exception page.
So I suppose it's a bug, I'll add a testcase to JIRA.
Adam -
6. Re: Exceptions in page param converters
adamw Oct 26, 2007 9:31 AM (in response to adamw)Posted in JIRA:
http://jira.jboss.org/jira/browse/JBSEAM-2163
Adam