[ 
https://issues.apache.org/jira/browse/SYNAPSE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Asankha C. Perera reopened SYNAPSE-394:
---------------------------------------

      Assignee: Asankha C. Perera

Asanka A

I do not think this patch was yet applied to the SVN? Hence this should not be 
marked resolved until such time

asankha

> FIX transport dose not handle a XML based FIX message payload with XML 
> namespace 
> ---------------------------------------------------------------------------------
>
>                 Key: SYNAPSE-394
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-394
>             Project: Synapse
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 1.2
>         Environment: Ubuntu-Gutsy 
>            Reporter: Asanka Abeysinghe
>            Assignee: Asankha C. Perera
>             Fix For: 1.3
>
>         Attachments: SYNAPSE-394.patch
>
>
> When a FIX message that defines in a XML structure with a namespace, will not 
> accept by the FIX transport layer. It fails when try to read the first 
> element of the SOAP message body.
> Sample input message: 
>                       <m0:message xmlns:m0="http://services.samples/xsd/";>
>                                               <m0:header>
>                                                  <m0:field 
> m0:id="35"><![CDATA[8]]></m0:field>
>                                                  <m0:field 
> m0:id="52"><![CDATA[20080618-08:41:56]]></m0:field>
>                                               </m0:header>
>                                               <m0:body>
> Current implementation uses QName(<tag name>) to fetch the elements instead 
> of using QName(<tag name>,<namespace URI>)                                    
>             

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to