java.lang.Exception: hl7:message attribute 'encodingStyle' is not well defined while attempting to process encoded data. Using the HL7 version 2.x XSD's download from the HL7BC page. Used the 2.3.1 ADT A43 schema just like the demo. Really like to demonstrate how Open ESB is so much better than JCAPS at this... Also get this message from deployment, ValidationException: The base type 'ST' was not found.

Oracle Community | 843830 | 9 years ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    HL7 Binding Components Open ESB build 20071230

    Oracle Community | 9 years ago | 843830
    java.lang.Exception: hl7:message attribute 'encodingStyle' is not well defined while attempting to process encoded data. Using the HL7 version 2.x XSD's download from the HL7BC page. Used the 2.3.1 ADT A43 schema just like the demo. Really like to demonstrate how Open ESB is so much better than JCAPS at this... Also get this message from deployment, ValidationException: The base type 'ST' was not found.

    Root Cause Analysis

    1. java.lang.Exception

      hl7:message attribute 'encodingStyle' is not well defined while attempting to process encoded data. Using the HL7 version 2.x XSD's download from the HL7BC page. Used the 2.3.1 ADT A43 schema just like the demo. Really like to demonstrate how Open ESB is so much better than JCAPS at this... Also get this message from deployment, ValidationException: The base type 'ST' was not found.

      at org.exolab.castor.xml.schema.ComplexType.validate()
    2. org.exolab.castor
      Schema.validate
      1. org.exolab.castor.xml.schema.ComplexType.validate(ComplexType.java:921)
      2. org.exolab.castor.xml.schema.Schema.validate(Schema.java:1562)
      2 frames