1 Reply Latest reply on Nov 7, 2005 4:38 PM by vianney

    Problems with Outjected variables in JSP

    gavin.king

      This should work, as long as the SeamVariableResolver is enabled.

        • 1. Re: Problems with Outjected variables in JSP
          vianney

          I do have the same problem actually.
          The SeamVariableResolver is enabled though proven by the fact my JSF page can access to my backing bean wchich is a Stateful SB annoted with @name but my JSF page cannot access to any of the variable annotated with @Out or @DataModel.

          As Peter, I wanted to plug Seam into our existing myfaces/struts-tiles application but if i can't use @DataModel annotations, i will give up.

          My StateFull SB is like this :

          @Stateful
          @Name("menuMgmt")
          @Scope(ScopeType.SESSION)
          @Interceptor(SeamInterceptor.class)
          @Conversational(ifNotBegunOutcome="list")
          public class MenuFacadeBean implements MenuFacadeLocal, Serializable {
          
           private static final Log log = LogFactory.getLog(MenuFacadeBean.class);
          
           @PersistenceContext(type=EXTENDED)
           private EntityManager entityManager;
          
           @DataModel
           private List<MenuItem> menuListModel;
          
           @DataModelSelectionIndex
           private int miIndex;
          
           @Out("menuItem")
           private MenuItem menuItem;
          
          


          and my log file only shows:
          INFO [org.jboss.seam.Component] Component: menuMgmt, scope: SESSION, type: STATEFUL_SESSION_BEAN, class: com.obsidium.omni.admin.session.MenuFacadeBean

          nothing about my @Out variable.

          I can run the booking example perfectly and i can see that Seam initialization detect the @out variables and the your pages can access to a @DataModel variable.

          Any ideas?