What happens if you remove the @Create annotation? Its pretty much just plain
wrong to have @Create @Factory together.
Seam's exception handling kicks in when you invoke a component method, not
during the instantiation cycle.
View the original post :
http://www.jboss.com/index.html?module=bb&o
Hi Gavin,
Thanks for the tip and help. Unfortunately, I get the same stack trace when I
remove the @Create annotation...
What's interesting (or maybe it's not that interesting) is that if I set the
Facelets development property to true:
| facelets.DEVELOPMENT
| true
|
then I
Oh, according to the stack trace this exception occurs in the render phase!
Of course Seam can most certainly not do anything at all about an exception
that occurs while rendering the view!
This is obvious, right? (Servlet engine may already have flushed some of the
response to the browser.)
V
This behavior is well-documented, btw:
http://docs.jboss.com/seam/1.1CR1/reference/en/html/events.html#d0e3555
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988595#3988595
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p
And so the correct way to solve your problem is to use a page action instead of
an @Factory method, since page actions take place *before* rendering the view.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988596#3988596
Reply to the post :
http://www.jboss.
Hi Gavin,
Thanks for the info. I was under the belief that the factory method would be
called in the invoke application phase... Are you saying that instantiations
take place in the render phase instead? I probably need to understand the JSF
lifecyle some more and JSF/Seam in general (I'm st
It happens when the variable is first referenced. In this case, during the
render phase.
Note that if this is a GET request, or a redirect, there is no invoke
application phase.
Use a page action.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988674#398867
