PM41749: FAILURE TO RESOLVE COMPONENTS WHEN LOADING SCHEMA DOCUMENTS

8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• Failure to resolve components when loading schema documents
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM Business Process Manager and            *
  *                  WebSphere Enterprise Service Bus            *
  *                  customers using Lazy Parsing Mode           *
  ****************************************************************
  * PROBLEM DESCRIPTION: Failure to resolve components when      *
  *                      loading schema documents                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Sometimes when schema documents are loaded, the following
  error is encountered:
  
  Cannot resolve the name '...' to a(n) 'type definition'
  component.
   at
  com.ibm.xml.xml4j.internal.s1.impl.XMLErrorReporter.reportError
   at
  com.ibm.xml.xml4j.internal.s1.impl.xs.traversers.XSDHandler.repo
  rtSchemaError
   at
  com.ibm.xml.xml4j.internal.s1.impl.xs.traversers.XSDHandler.repo
  rtSchemaError
   at
  com.ibm.xml.xml4j.internal.s1.impl.xs.traversers.XSDHandler.getG
  lobalDecl
   at
  com.ibm.xml.xml4j.internal.s1.impl.xs.traversers.XSDElementTrave
  rser.traverseNamedElement
   at
  com.ibm.xml.xml4j.internal.s1.impl.xs.traversers.XSDElementTrave
  rser.traverseLocal
   at
  com.ibm.xml.xml4j.internal.s1.impl.xs.traversers.XSDHandler.trav
  erseLocalElements
   at
  com.ibm.xml.xml4j.internal.s1.impl.xs.traversers.XSDHandler.pars
  eSchema
   at
  com.ibm.xml.xml4j.internal.s1.impl.xs.XMLSchemaLoader.loadSchema
   at
  com.ibm.xml.xml4j.internal.s1.impl.xs.XMLSchemaLoader.loadGramma
  r
   at
  com.ibm.xml.xml4j.internal.s1.parsers.XMLGrammarPreparser.prepar
  seGrammar
   at
  com.ibm.xml.xci.internal.util.resources.XSDGrammarResource.load
   at com.ibm.xml.xci.type.TypeRegistry.performSchemaLoad
   at com.ibm.xml.xci.type.TypeRegistry.load
  

Problem conclusion

• The schema loading code was mistakenly treating two different
  schema documents as the same, and ignored one of them as a
  result. Any reference to schema components defined in the
  ignored schema document could not be resolved. The code has
  been improved to treat the schema document as distinct to load
  the required schema components.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.1.  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 is sysrouted FROM one or more of the following:

  PM39306

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

Fix information

• Fixed component name

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R800 PSY