glassfish
  1. glassfish
  2. GLASSFISH-18514

CDI does not get enabled on server start for a WAB bundle, the war has to be redeployed after the server starts for CDI to be enabled.

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Critical Critical
    • Resolution: Unresolved
    • Affects Version/s: 3.1.2
    • Fix Version/s: future release
    • Component/s: cdi, OSGi-JavaEE
    • Labels:
      None

      Description

      CDI does not get enabled on server start for a WAB bundle, the war has to be redeployed after the server starts for CDI to be enabled.

      Please see attached server.log

      You can see after the server has started I manually redeployed the WAB and CDI was enabled that time.

      If I do not redeploy the WAB CDI is not enabled and I get NPE when trying to access a JAX-RS resource that @Inject's a @OSGiService(dynamic=true).

      1. server.log
        110 kB
        aaronjwhiteside

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Sivakumar Thyagarajan
            Reporter:
            aaronjwhiteside
          • Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated: