You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Alex Boisvert (JIRA)" <ji...@apache.org> on 2009/08/20 19:14:15 UTC
[jira] Resolved: (ODE-655) OdeSUManager - component-task-result
parsing errors during startup
[ https://issues.apache.org/jira/browse/ODE-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Boisvert resolved ODE-655.
-------------------------------
Resolution: Fixed
I rolled back the changes made in ODE-643
> OdeSUManager - component-task-result parsing errors during startup
> ------------------------------------------------------------------
>
> Key: ODE-655
> URL: https://issues.apache.org/jira/browse/ODE-655
> Project: ODE
> Issue Type: Bug
> Components: JBI Integration
> Environment: Fuse-3.4.0.4, WinXP, Apache ODE 1.x branch rev 806132
> Reporter: Mateusz Nowakowski
> Fix For: 1.3.4
>
>
> When ODE starts it prints to the standard output:
> Starting Apache ServiceMix ESB: 3.4.0.4-fuse
> Loading Apache ServiceMix from servicemix.xml on the CLASSPATH
> [Fatal Error] :2:140: Attribute "xmlns" bound to namespace "http://www.w3.org/2000/xmlns/" was already specified for element "component-task-result".
> [Fatal Error] :2:140: Attribute "xmlns" bound to namespace "http://www.w3.org/2000/xmlns/" was already specified for element "component-task-result".
> [Fatal Error] :2:140: Attribute "xmlns" bound to namespace "http://www.w3.org/2000/xmlns/" was already specified for element "component-task-result".
> [Fatal Error] :2:140: Attribute "xmlns" bound to namespace "http://www.w3.org/2000/xmlns/" was already specified for element "component-task-result".
> I'd like to reopen ODE-653, but I'm unable to do it. This is probably caused by ODE-653 patch.
> PS. Branch 1.x creates ode-jbi-1.3.2-SNAPSHOT.zip instead of ode-jbi-1.3.4-SNAPSHOT.zip
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Resolved: (ODE-655) OdeSUManager - component-task-result
parsing errors during startup
Posted by Greg Lucas <gr...@gmail.com>.
Hi Alex,
Can you take another look at this? I had revised the patch to remove
the unnecessary attribute that caused the problem.
Thanks,
--
Greg
Re: [jira] Resolved: (ODE-655) OdeSUManager - component-task-result
parsing errors during startup
Posted by Greg Lucas <gr...@gmail.com>.
Thanks Alex! I'll update patch after testing with both FUSE 3.4 and 4.1.
~Greg
On Thu, 20 Aug 2009 13:14:15 -0400, Alex Boisvert (JIRA) <ji...@apache.org>
wrote:
>
> [
> https://issues.apache.org/jira/browse/ODE-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Alex Boisvert resolved ODE-655.
> -------------------------------
>
> Resolution: Fixed
>
> I rolled back the changes made in ODE-643
>
>> OdeSUManager - component-task-result parsing errors during startup
>> ------------------------------------------------------------------
>>
>> Key: ODE-655
>> URL: https://issues.apache.org/jira/browse/ODE-655
>> Project: ODE
>> Issue Type: Bug
>> Components: JBI Integration
>> Environment: Fuse-3.4.0.4, WinXP, Apache ODE 1.x branch rev
>> 806132
>> Reporter: Mateusz Nowakowski
>> Fix For: 1.3.4
>>
>>
>> When ODE starts it prints to the standard output:
>> Starting Apache ServiceMix ESB: 3.4.0.4-fuse
>> Loading Apache ServiceMix from servicemix.xml on the CLASSPATH
>> [Fatal Error] :2:140: Attribute "xmlns" bound to namespace
>> "http://www.w3.org/2000/xmlns/" was already specified for element
>> "component-task-result".
>> [Fatal Error] :2:140: Attribute "xmlns" bound to namespace
>> "http://www.w3.org/2000/xmlns/" was already specified for element
>> "component-task-result".
>> [Fatal Error] :2:140: Attribute "xmlns" bound to namespace
>> "http://www.w3.org/2000/xmlns/" was already specified for element
>> "component-task-result".
>> [Fatal Error] :2:140: Attribute "xmlns" bound to namespace
>> "http://www.w3.org/2000/xmlns/" was already specified for element
>> "component-task-result".
>> I'd like to reopen ODE-653, but I'm unable to do it. This is probably
>> caused by ODE-653 patch.
>> PS. Branch 1.x creates ode-jbi-1.3.2-SNAPSHOT.zip instead of
>> ode-jbi-1.3.4-SNAPSHOT.zip
>
--
Greg Lucas