2 Replies Latest reply on Nov 14, 2006 6:46 PM by Pete Muir

    seam component not found: user

    Arnie Morein Novice

      I used to have this working but now it doesn't. When I click the Login button on my form, I'm getting an error back on the user name field of "conversion error". My guess is its getting a null pointer exception because seam isn't creating the user object before trying to populate the variables:


      2006-11-07 10:53:51,031 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] resolving name: user
      2006-11-07 10:53:51,031 DEBUG [org.jboss.seam.Component] seam component not found: user
      2006-11-07 10:53:51,031 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] could not resolve name
      2006-11-07 10:53:51,125 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] resolving name: user
      2006-11-07 10:53:51,125 DEBUG [org.jboss.seam.Component] seam component not found: user
      2006-11-07 10:53:51,125 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] could not resolve name


      My project has:

      User.class - just a pojo, NOT an entity (the data is loaded from LDAP, just for authentication and authorization)
      Userlogin & UserLoginAction - displays the login form and attempts the login, which handled by using the injected User object which just holds the form field values and the resultant LDAP info IF they authenticate.

      Apparently, seam cannot find the User class. Its in the EJB.jar file, there is a seam.properties file in the jar. User as a @Name("user") annotation. I've tried User and user (is seam case sensitive?


      I don't envision UserLogin sticking around but its currently:
      @Stateful
      @Name("userLogin")
      @Scope(ScopeType.CONVERSATION)
      public class UserLoginAction implements UserLogin ...

      But I still cannot get it to work. Is every class that I need to be "injected" by Seam going to have to be an EJB3 "stateful" class?