Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-4026

add a configuration attribute to @WebContext to handle EJB3 loadOnStartup > -1 situations

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Obsolete
    • Icon: Major Major
    • None
    • 9.0.0.Alpha1
    • EJB
    • None

      An app with a servlet that is loadOnStartup = 1 that references an EJB3 webservice not defined by a WSDL fails because the EJB3 servlet does not have the same loadOnStartup designator. There is an existing wildFly integration test that demonstrates this. (see org.jboss.as.test.integration.ws.serviceref.ServiceRefWithoutExplicitWsdlServletTestCase)
      Also see the original bug filed against this behavior and the comments on the
      cause, https://issues.jboss.org/browse/WFLY-3262.
      A suggested solution is to add a configuration attribute to @WebContext.

              Unassigned Unassigned
              rsearls r searls
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: