Uploaded image for project: 'Application Server 7'
  1. Application Server 7
  2. AS7-2961

Context lookup fails during WebService constructor.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.1.0.CR1
    • 7.1.0.Beta1
    • Web Services
    • None
    • Hide

      Build the provided web application using Maven. The application supports using arquillian to load and deploy the application.

      When the application is deployed a stack trace will be displayed.

      Show
      Build the provided web application using Maven. The application supports using arquillian to load and deploy the application. When the application is deployed a stack trace will be displayed.
    • Hide

      None.

      Show
      None.
    • Low

    Description

      During a WebService constructor call my application is making a jndi context lookup that is failing. The lookup uses java:comp/env to lookup an entry. The web service is a JEE5 spec application.

      The application defines an env-entry in the web deployment descriptor.
      It looks as though the context is not established in time for the WebSevice constructor being called.

      A sample application is provided to demonstrate the issue. When this application is deployed I am seeing the stack trace in the second attachment.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. AS7-2922 If nothing is bound to java:comp/env the java:comp/env context cannot be looked up

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. AS7-2184 persistence.xml java:comp/env lookup fails during deployment because ContextInitialized is not complete

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. AS7-3823 Remove JBossWS JNDI hacks not needed anymore

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              ropalka Richard Opalka
              jwhiting@redhat.com Jeremy Whiting
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: