[
https://issues.apache.org/activemq/browse/SMX4-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53597#action_53597
]
Greg Lucas commented on SMX4-321:
---------------------------------
I have a patch for this but am wondering about something in the spec. The
Apache ODE ServiceUnitManager returns a result string that does not include the
xmlns declaration for the jbi/management-message namespace. In smx3 we treat
this as an invalid result string and ignore it. However, the example in the JBI
spec itself (the doc for ServiceUnitManager.deploy) leaves off the namespace
declaration on the top element.
We could allow this - e.g. hack the result string to add a wrapper element and
declare the default namespace before parsing. I've been doing that anyway to
test with Ode. Or we could just say the spec is misleading and the result
string must fully conform to the schema. Any opinions? I can provide the patch
with/without the wrapper. Either way, I'll file a defect with ODE to produce
result strings with namespace declarations.
> Component task result from ServiceUnitManager.deploy is ignored
> ---------------------------------------------------------------
>
> Key: SMX4-321
> URL: https://issues.apache.org/activemq/browse/SMX4-321
> Project: ServiceMix 4
> Issue Type: Bug
> Reporter: Greg Lucas
>
> In SMX3 the result from ServiceUnitManager.deploy was examined to determine
> the task result (SUCCESS or otherwise). As the JBI spec implies, this allows
> either a DeploymentException or a task-result of FAILED to signal a
> deployment failure.
> In SMX4 the task result is being ignored and deployment is considered
> successful unless an exception is thrown.
> See http://issues.apache.org/jira/browse/ODE-635 where this issue was
> originally raised; the ODE ServiceUnitManager does not throw an exception
> and so deployment failures are not detected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
