TomEE
  1. TomEE
  2. TOMEE-35

Unable to lookup BeanManager from JNDI

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.0.0-beta-1
    • Fix Version/s: 1.0.0-beta-2
    • Component/s: None
    • Labels:
      None
    • Environment:
      Seam 3.1.0-SNAPSHOT

      Description

      See the attached application and stack trace for details.

      1. wicket-numberguess-u1.war
        2.61 MB
        Jozef Hartinger
      2. wicket-numberguess.txt
        2 kB
        Jozef Hartinger
      3. wicket-numberguess.war
        2.61 MB
        Jozef Hartinger
      4. config-quiz.war
        1.26 MB
        Jozef Hartinger
      5. quiz.txt
        1 kB
        Jozef Hartinger

        Activity

        Hide
        Romain Manni-Bucau added a comment -

        here the exception:

        java.lang.NoClassDefFoundError: Lorg/jboss/seam/persistence/PersistenceContexts;

        Show
        Romain Manni-Bucau added a comment - here the exception: java.lang.NoClassDefFoundError: Lorg/jboss/seam/persistence/PersistenceContexts;
        Hide
        Romain Manni-Bucau added a comment -

        did you resolve the issue?

        Show
        Romain Manni-Bucau added a comment - did you resolve the issue?
        Hide
        Jozef Hartinger added a comment -

        Another application I am able to reproduce the problem with. This time there is no other exception in any of the log files.

        Show
        Jozef Hartinger added a comment - Another application I am able to reproduce the problem with. This time there is no other exception in any of the log files.
        Hide
        Romain Manni-Bucau added a comment -

        it is because your provided in your application a META-INF/services/javax.el.ExpressionFactory file with a non existing file.

        Show
        Romain Manni-Bucau added a comment - it is because your provided in your application a META-INF/services/javax.el.ExpressionFactory file with a non existing file.
        Hide
        Jozef Hartinger added a comment -

        Thanks, I must have missed that.

        Show
        Jozef Hartinger added a comment - Thanks, I must have missed that.
        Hide
        Romain Manni-Bucau added a comment -

        no worries

        Show
        Romain Manni-Bucau added a comment - no worries
        Hide
        Jozef Hartinger added a comment -

        Even without the the service provider file I am getting the same exception.

        Show
        Jozef Hartinger added a comment - Even without the the service provider file I am getting the same exception.
        Hide
        Romain Manni-Bucau added a comment -

        could you detail a bit more where and when you are looking up the bean manager.

        the BM is not always available in a JEE container (if i remember it has to be available only in JEE components)

        Show
        Romain Manni-Bucau added a comment - could you detail a bit more where and when you are looking up the bean manager. the BM is not always available in a JEE container (if i remember it has to be available only in JEE components)
        Hide
        Romain Manni-Bucau added a comment -

        with the last version (should be compiling just now) i got:

        java.lang.NoClassDefFoundError: org/jboss/weld/Container
        org.jboss.seam.wicket.SeamRequestCycle.instance(SeamRequestCycle.java:116)
        org.jboss.seam.wicket.SeamRequestCycle.detach(SeamRequestCycle.java:104)
        org.apache.wicket.RequestCycle.steps(RequestCycle.java:1462)
        org.apache.wicket.RequestCycle.request(RequestCycle.java:545)
        org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:486)
        org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:319)

        Show
        Romain Manni-Bucau added a comment - with the last version (should be compiling just now) i got: java.lang.NoClassDefFoundError: org/jboss/weld/Container org.jboss.seam.wicket.SeamRequestCycle.instance(SeamRequestCycle.java:116) org.jboss.seam.wicket.SeamRequestCycle.detach(SeamRequestCycle.java:104) org.apache.wicket.RequestCycle.steps(RequestCycle.java:1462) org.apache.wicket.RequestCycle.request(RequestCycle.java:545) org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:486) org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:319)
        Hide
        Romain Manni-Bucau added a comment -

        your application doesn't work but the bean manager can be looked-up from JNDI.

        In your dependency seam-wicket, you need the weld container which is not (and will not be) delivered with TomEE. I think you should open an issue on the seam wicket jira: https://issues.jboss.org/browse/SEAMWICKET/

        Show
        Romain Manni-Bucau added a comment - your application doesn't work but the bean manager can be looked-up from JNDI. In your dependency seam-wicket, you need the weld container which is not (and will not be) delivered with TomEE. I think you should open an issue on the seam wicket jira: https://issues.jboss.org/browse/SEAMWICKET/
        Hide
        Jozef Hartinger added a comment -

        Where did you get that log message from? I cannot see it in any of the log files. Do I need to tweak log levels to get that info?

        Show
        Jozef Hartinger added a comment - Where did you get that log message from? I cannot see it in any of the log files. Do I need to tweak log levels to get that info?
        Hide
        Romain Manni-Bucau added a comment -

        i simply uncommented console logger in logging.properties (end of the logging.properties file) and used info level instead of fatal

        Show
        Romain Manni-Bucau added a comment - i simply uncommented console logger in logging.properties (end of the logging.properties file) and used info level instead of fatal

          People

          • Assignee:
            Romain Manni-Bucau
            Reporter:
            Jozef Hartinger
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development