Description:
Defect 1-16PDDS
ebxmltools failed to load nested schemas properly when the XSDs reside on a different drive than where ebxmltools is. This is now fixed.

Defect 1-17ILD0
Incoming business exception messages that contain extended XML namespace elements were failing to validate. This is
now relaxed where the extended XML namespace data are processed using the processContent='lax' rule.

Defect 1-1N8ZDR
When Response Action's "Require Non-repudiation of Response" is selected all outgoing business-level responses were to be signed.
However, outgoing business Exception messages were not signed. This is now fixed.

Defect 1-1P6RUH
When operationID is used in the InitiatorRequest message instead of the combination of organization, businessProcess, businessProcess
Version, and transactionName then the above individual attributes were missing in InitiatorAck and InitiatorResponse messages. This error
condition is particularly obvious when BusinessWorks is used to initiate an outgoing request. This is now fixed.

Defect 1-1P6RUW
ebXML BusinessWorks plugin was not subscribing the Advisory messages using the correct subject name. This is now fixed.

Defect 1-1P6RVA
When non-default TIB/Rendezvous parameters, such as network and service, are used there were a couple of bus transport initialization
errors being reported. These were harmless as these transports were not used. This is now fixed so as not to cause any alarm.

NOTE: For this hotfix to take effect BC 3.5.0 hotfix#5 is also required.

Defect 1-1P6RVP
ebxmlclient.jar was not working properly when used in BusinessWorks 5.1. BC/ebXML would fail to receive data properly. This is now fixed.