[jboss-user] [JBoss Seam] - lost injected entity bean

2008-02-03 Thread kitada21
When multiple access, lost injected entity bean. 1.currentUser not null if(currentUser == null){ 2.currentUser not null log.debug("■standardPageAction:" + currentUser.getUserId()); 3.currentUser is null String retPage = userEvent(currentUser.getUserId()); What's happened. I'm using Sea

[jboss-user] [JBoss Seam] - @In attribute requires non-null value

2008-02-03 Thread kitada21
When multiple accesss, @In failed after @Out. When Single access, no problem. 1.Outject currentUser. @In(required = false) @Out(required = true, scope = SESSION) User currentUser; 2.Inject currentUser. @In private User currentUser; 3.Exception occured.

[jboss-user] [JBoss Seam] - Re: @In attribute requires non-null value

2008-02-04 Thread kitada21
Thank you for your response. I will try debugging, but I'm anxious about the results becouse single access or few multiple access is no problem. I'm thinking now that the same cause of my another topic. http://www.jboss.com/index.html?module=bb&op=viewtopic&t=129224 Informtion: I using JMete

[jboss-user] [JBoss Seam] - Re: lost injected entity bean

2008-02-04 Thread kitada21
Sorry, I can not judge that two topic was same problem. You think same problem? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126429#4126429 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126429 _

[jboss-user] [JBoss Seam] - Re: @In attribute requires non-null value

2008-02-04 Thread kitada21
Certainly, the Identity is never used. My authentication process is three step. 1.Tomcat Authentication used by FORM:org.jboss.web.tomcat.security.ExtendedFormAuthenticator 2.Seam Authentication used by Identity:SessionManager class 3.Own application Authentication used by RDB:Authenticator