Resolution:
Description:
=========

When running be-oradeploy.exe to generate the backing store schema, it throws a Null pointer exception. Sometimes this behavior is exhibited when running TIBCO BusinessEvents (BE) projects that are migrated from BE 3.x to version 4.x.

Stack trace/excerpts from the Nullpointer exception "

java.lang.NullPointerException
        at com.tibco.xml.schema.impl.DefaultComponent.shallowClone(DefaultComponent.java:416)
        at com.tibco.xml.schema.impl.DefaultNamedComponent.shallowClone(DefaultNamedComponent.java:215)
        at com.tibco.xml.schema.impl.DefaultDataComponent.shallowClone(DefaultDataComponent.java:61)
        at com.tibco.xml.schema.impl.DefaultElement.shallowClone(DefaultElement.java:46)
        at com.tibco.xml.schema.impl.DefaultComponent.resolveComponent(DefaultComponent.java:277)


Environment:
==========

   o TIBCO BusinessEvents 4.0 - Enterprise Edition

   o BE Projects migrated from 3.x to version 4.x .
  
   o All OS

Resolution:
=========

This error generally occurs when multiple schema files define the same conflicting element. The solution is to remove the xsd/schema file that is not needed.  This error may or may not cause a runtime issue, depending on how those schema elements are used.