Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-7935

[GSS](7.0.z) JBWS-4046 - PostConstruct method not invoked on web service handler

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.0.6.CR1, 7.0.6.GA
    • 7.0.3.GA
    • None
    • None
    • Workaround Exists
    • Hide

      Yes, you can avoid the bug by not giving the webservices the same name and namespace, but the customer says they cannot do this as this is how they implement their versioning of webservices.

      Show
      Yes, you can avoid the bug by not giving the webservices the same name and namespace, but the customer says they cannot do this as this is how they implement their versioning of webservices.
    • Hide

      1. Deploy demo-webservice.zip (attached).
      2. Using SoapUI call both deployed webservices.
      3. One will return successfully, the other will give an error message of "postconstruct method was not invoked!".

      Show
      1. Deploy demo-webservice.zip (attached). 2. Using SoapUI call both deployed webservices. 3. One will return successfully, the other will give an error message of "postconstruct method was not invoked!".
    • EAP 7.0.6

      From support case:


      The attached demo WAR (source) contains two identical web services classes in different packages, which corresponds to our versioning layout used in production. Both web services use the same handler class. However, the handler's PostConstruct method is only executed for invocations of one of the two web services (expected: for invocations of both web services).

      This error could theoretically be worked around by renaming one of the web services, or by changing one of the target namespaces. However, this is not an option for our production purposes.

      This error did not show up in EAP 6.4.9 and earlier versions.


      Essentially they have two webservices both annotated identically with:
      @WebService(name = "DemoService", targetNamespace = "http://demo.svc.co.at")
      but they are exposed at different URLs through their web.xml file

      In EAP 6.4.x this works fine. In EAP 7.x only one version calls PostConstruct method, presumably the first one deployed. So, this appear to be a regression.

              spyrkob Bartosz Spyrko-Smietanko
              spyrkob Bartosz Spyrko-Smietanko
              Peter Mackay Peter Mackay
              Peter Mackay Peter Mackay
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: