IBM Support

PM72860: Optionally allow webservices annotation scanning to occur if metadata-complete is set to true

Fixes are available

7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Optionally allow the webservice annotation scan to occur even
    if metadata-complete is set to true in the module deployment
    descriptor.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server users of   *
    *                  JAX-WS web services using metadata-         *
    *                  complete                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: When metadata-complete is set on a      *
    *                      module, this blocks detection of        *
    *                      JAX-WS webservices.                     *
    ****************************************************************
    * RECOMMENDATION:  Install a fix pack containing this APAR.    *
    ****************************************************************
    Users that want to set metadata-complete on modules find that
    JAX-WS web services are no longer detected.
    

Problem conclusion

  • Specifying metadata-complete causes WebSphere Application
    Server to use only deployment descriptor information written
    in XML files when deploying or starting an application, and
    not perform annotation scanning. The JAX-WS specification does
    not provide any way to express the existence of webservice
    classes in these files.  As a result, if a module is not
    scanned for annotations, JAX-WS web services will not be
    detected and will not be operable.
    
    In scenarios where it is desired to use metadata-complete but
    also detect JAX-WS web services, the JVM property
    jaxws.ignoreMetadataComplete can be set to true.  This will
    cause an annotation scan to be performed for web services
    regardless of the setting of metadata-complete.
    
    This property must be set as a JVM system property and must be
    set on every JVM where the JAX-WS application is deployed and
    also on its corresponding deploy manager and node agent.
    
    If an installed application did not have JAX-WS services
    detected, and then this JVM property is set to true, it will
    be necessary to uninstall and reinstall the application for
    detection to occur.  This is because detection of JAX-WS
    services is a deploy-time event.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.27, 8.0.0.6 and 8.5.0.2  Please refer to the
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM72860

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-09-13

  • Closed date

    2012-10-10

  • Last modified date

    2013-03-06

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R700 PSY

       UP

  • R800 PSY

       UP

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM72860

Modified date: 06 March 2013