IBM Support

PM11727: MARKING METADATA-COMPLETE CAUSES LOSS OF NAMESPACE FROM WEB.XML

Fixes are available

7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
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
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
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

  • When deploying an application which contains a web module, where
    the web module contains a deployment descriptor (web.xml) having
    metadata-complete set to false, and containing a namespace value
    on a qualified name element, after changing metadata-complete to
    true, the update to web.xml removes the namespace value.
    Following, any use of the web.xml data will see an incomplete
    qualified name,typically resulting in exceptions or other
    failures while performing processing using the incomplete
    qualified name.
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server who imbed namespace values in        *
    *                  module metadata.                            *
    ****************************************************************
    * PROBLEM DESCRIPTION: When deploying a web module which       *
    *                      contains namespace values attached      *
    *                      to qualified name elements of the web   *
    *                      module deployment descriptor            *
    *                      (WEB-INF/web.xml), namespace values are *
    *                      dropped from web modules                *
    *                      metadata.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The problem manifests as a call to
    org.eclipse.jst.j2ee.common.QName.getNamespaceURI() which does
    not return the correct namespace value.  When this problem
    occurs, the prefix value value is returned instead of the
    namespace value.
    
    For example, for a web module deployment descriptor which
    contains the XML text:
    
    <service-qname
    xmlns:pfx="http://www.ibm.com/xmlns/prod/websphere/portal/wsrp/w
    sdl">pfx:WSRPService</service-qname>
    
    What should be returned is the value namespace value
    "http://www.ibm.com/xmlns/prod/websphere/portal/wsrp/wsdl",
    but what is actually returned is the prefix value "pfx".
    
    The problem is most detectable for web module which has a
    deployment descriptor that uses the
    schem ahttp://java.sun.com/xml/ns/javaee/web-app_2_5.xsd, as
    from the Servlet 2.5 Specification, and for which
    "metadata-complete" is false.
    
    If, following the deployment, the metadata-complete flag is
    updated to true, an update to the web module descriptor will be
    written.  The updated descriptor will be missing the namespace
    value.
    
    From the example, the following will be written:
    
    <service-qname>pfx:WSRPService</service-qname>
    

Problem conclusion

  • This problem occurred because a step of copying the module
    metadata did not copy the namespace value recorded within the
    module metadata. The copy failure occurred because the storage
    of the namespace value did not have visibility to the copy code.
    
    The problem was fixed by updating the copy code to include
    additional steps that copy the namespace value.
    
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.1.0.13.  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

    PM11727

  • 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

    2010-04-07

  • Closed date

    2010-05-25

  • Last modified date

    2010-05-25

  • 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



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM11727

Modified date: 25 May 2010