1 Reply Latest reply on Mar 12, 2007 11:02 AM by Norman Richards

    jboss-seam.jar and jboss lib directory

    Tom Goring Apprentice


      Hi can someone explain to me why (in a working web app) if I remove:


      from my EAR and module list in application.xml
      and just place the jars in my jboss/lib dir I get the below stack trace when I invoke a page.

      I.e. why to they need to go in the EAR file ?

      3:23:25,562 ERROR [[jsp]] Servlet.service() for servlet jsp threw exception
      javax.faces.el.EvaluationException: Cannot get value for expression '#{jnetFuiLogin.instance.userName}'
      at org.apache.myfaces.el.ValueBindingImpl.getValue(ValueBindingImpl.java:402)
      at javax.faces.component.UIOutput.getValue(UIOutput.java:77)
      at org.apache.myfaces.shared_impl.renderkit.RendererUtils.getStringValue(RendererUtils.java:217)
      at org.apache.myfaces.shared_impl.renderkit.html.HtmlTextRendererBase.renderInput(HtmlTextRendererBase.java:135)
      at org.apache.myfaces.shared_impl.renderkit.html.HtmlTextRendererBase.encodeEnd(HtmlTextRendererBase.java:53)
      at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:536)
      at javax.faces.webapp.UIComponentTag.encodeEnd(UIComponentTag.java:495)

        • 1. Re: jboss-seam.jar and jboss lib directory
          Norman Richards Master

          Seam is not designed to be shared between different applications. If you tried to share Seam, I assume you'd see a shared application context with component conflicts between the two. I'd also imagine you'd see scanning and classloading problems too. The short story is that Seam should be treated as an application-specific library and not shared.