IBM Support

PI11849: 'ORG.ECLIPSE.EMF.ECORE.XMI.FEATURENOTFOUNDEXCEPTION: FEATURE 'XMLNS' NOT FOUND' ERROR.

Fixes are available

7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
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.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
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.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
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.45: Java SDK 1.6 SR16 FP60 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
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Use of the namespace with an empty value <changeSummary
    xmlns=""> causes the following Exception.
    
    Caused by: org.eclipse.emf.ecore.xmi.FeatureNotFoundException:
    Feature 'xmlns' not found.
     at
    org.eclipse.emf.ecore.xmi.impl.XMLHandler.reportUnknownFeature(X
    MLHandler.java:1747)
     at
    org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleUnknownFeature(X
    MLHandler.java:1711)
     at
    org.eclipse.emf.ecore.xmi.impl.XMLHandler.setAttribValue(XMLHand
    ler.java:2449)
     at
    org.eclipse.emf.ecore.xmi.impl.SAXXMLHandler.handleObjectAttribs
    (SAXXMLHandler.java:78)
     at
    org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObjectFromFactor
    y(XMLHandler.java:1948)
     at
    org.eclipse.emf.ecore.sdo.util.DataGraphResourceFactoryImpl$1.cr
    eateObjectFromFactory(DataGraphResourceFactoryImpl.java:647)
     at
    org.eclipse.emf.ecore.sdo.util.DataGraphResourceFactoryImpl$1.ha
    ndleFeature(DataGraphResourceFactoryImpl.java:503)
     at
    org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XMLHand
    ler.java:888)
     at
    org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHandle
    r.java:867)
     at
    org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHandle
    r.java:635)
     at
    org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
    Source)
     at
    org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartE
    lement(Unknown Source)
     at
    org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentCo
    ntentDispatcher.dispatch(Unknown Source)
     at
    org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocume
    nt(Unknown Source)
     at
    org.apache.xerces.parsers.XML11Configuration.parse(Unknown
    Source)
     at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown
    Source)
     at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
     at
    org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
    Source)
     at javax.xml.parsers.SAXParser.parse(Unknown Source)
     at
    org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl.java
    :179)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: A FeatureNotFoundException is           *
    *                      received while processing an XML file   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A "feature not found" exception may be received while
    processing an "xmlns" or "xsitype" attribute of an XML element
    using the SAX parser.
    The exception occurs when using the Eclipse EMF libraries to
    process XML data, with the SAX parser selected as the XML
    parser, and with the SAX parser configured with namespace
    processing disabled and namespace-prefixes enabled.  That is,
    with a feature configuration where
    http://xml.org/sax/features/namespaces is 'false' and
    http://xml.org/sax/features/namespace-prefixes is 'true'.
    Having namespace processing disabled and namespace-prefixes
    enabled is not the default configuration which is used by the
    application server.  Therefore the exception should not occur
    from application server code but is mostly likely from stacked
    product or application code.
    

Problem conclusion

  • The Eclipse EMF XML parsing code was incorrectly determining
    if namespace processing was enabled and handling attributes as
    if it was enabled when it was not.
    
    The component which detects if namespace processing is enabled
    has been updated to use the features described above to
    determine the state of namespace processing.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.35, 8.0.0.10, and 8.5.5.4.  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

    PI11849

  • 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

    2014-02-16

  • Closed date

    2014-07-22

  • Last modified date

    2014-07-22

  • 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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022