[ODE-653] OdeSUManager produces component-task-result strings that are not fully compliant.

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.3.3
• Fix Version/s: 1.3.4
• Component/s: JBI Integration
• Assignee: Unassigned
• Reporter: Greg Lucas
• Created: 19/Aug/09 17:20
• Updated: 21/Sep/09 18:15
• Resolved: 21/Sep/09 18:12

Description

The JBI spec specifies that a ServiceUnitMnager must return an XML string of the component-task-result for the deploy/undeploy methods. The component-task-result must conform to the http://java.sun.com/xml/ns/jbi/management-message schema.

The OdeSUManager currently returns component-task-result strings that do not declare the namespace, so parsing these strings produces an XML document that does actually conform to the schema in the spec.

ServiceMix will treat these result strings as invalid and ignore them. I've submitted an SMX4 patch to handle the case where no namespace is declared, but think that ODE should fully conform to the spec regardless of whether that patch gets applied.

(Note that the ServiceUnitManager javadoc is a bit misleading as the example it shows has the xmlns declaration on the wrong node. I think the text of the JBI spec is more authoritative and would consider the example in the javadoc incorrect as well. The ODE result string doesn't match the example either.)

Issue Links

• is cloned by: ODE-655 OdeSUManager - component-task-result parsing errors during startup