I encountered the same problem in my J2EE application, which uses Seam
2.0.0.GA. It is caused by a bug in JBoss/Seam. See the JIRA issues JBSEAM-2214
and JBSEAM-2224. I got rid of the problem by installing the fix
(EntityBeanList.java version 1.6).
View the original post :
http://www.jboss.com
"thejavafreak" wrote : 1. Perhaps because the conversation has ended, or it has
reached the maximum time-out
| 2. Perhaps it's on a different conversation, make sure it has the same
conversation id
Sorry, I don't understand this.
The component instance is the same when I return to the view. Onl
1. Perhaps because the conversation has ended, or it has reached the maximum
time-out
2. Perhaps it's on a different conversation, make sure it has the same
conversation id
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079452#4079452
Reply to the post :
ht
