When you deploy your app, Seam tells you the component it found. Look there. My
guess is that it is something else.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3954604#3954604
Reply to the post :
Model update is a JSF lifecycle phase, it has nothing to do with entity
persistence.
I've found model update errors often occur when the object it refers to is
null, but I would suggest using the debugger to find out more
Depending on the setting of hibernate.hbm2ddl.auto in persistence.xml
anonymous wrote : Model update is a JSF lifecycle phase
I agree with this. But if there is an error in the application (lifecycle,
persistence or whatever), I need to see the exception in the log and a stack
trace. First for debugging purposes and later for monitoring the application in
It seems like seam cannot locate my user variable in the contexts. Actualy it
seems like it can't even locate the class annotated with @Name(user):
| 15:31:18,155 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] resolving
name: user
| 15:31:18,155 DEBUG [org.jboss.seam.Component] seam
free67 wrote : anonymous wrote : Model update is a JSF lifecycle phase
| I agree with this. But if there is an error in the application (lifecycle,
persistence or whatever), I need to see the exception in the log and a stack
trace.
And of course you will. Seam does not swallow any exceptions,
free67 wrote : It seems like seam cannot locate my user variable in the
contexts. Actualy it seems like it can't even locate the class annotated with
@Name(user):
| Am I reading this right? and if yes, should it not throw an Exception?
|
Probably Seam has not installed your user component.
King, you say I say Seam is evil!?! Of course it is. How else do you expect it
to take over the world.
You are right. Seam does not swallow exceptions and... I never mentioned
swallowing in my post. blah, that's so anticlimactic.
Fine, this is just the way faces is designed and also the way
Every now and then I come aross this error. I found the easiest way to
fix/workaround this error is to add a @Name annotation to your Entity.
ie:
@Name(supplier)
Hope this helps.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3938256#3938256
Reply to the
please if somebody has more information, can post here because I have this same
error after some changes, and not a clue yet...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3937748#3937748
Reply to the post :
what did you do?
I am having the same problem and it's driving me crazy...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3931371#3931371
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3931371
IT seems that faces did not call the action at all. Even in the simple action
without method call it is not working!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3917870#3917870
Reply to the post :
I got a new clue. Lowering the bug level to debug I got
18:45:08,040 DEBUG [VariableResolverImpl] Variable 'person' could not be
resolved.
18:45:08,041 DEBUG [VariableResolverImpl] Variable 'person' could not be
resolved.
person is the entity bean in the form.
But I couldn't figure out why it
Solved!
Myfaces bug I guess
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3917886#3917886
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3917886
---
This SF.net email is
13 matches
Mail list logo
