synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dushan Sachinda Abeyruwan (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SYNAPSE-891) FIX message builder /formatter
Date Fri, 13 Jul 2012 04:33:33 GMT
Dushan Sachinda Abeyruwan created SYNAPSE-891:
-------------------------------------------------

             Summary: FIX message builder /formatter
                 Key: SYNAPSE-891
                 URL: https://issues.apache.org/jira/browse/SYNAPSE-891
             Project: Synapse
          Issue Type: Improvement
          Components: Transports
    Affects Versions: 2.1
         Environment: Ubuntu 12.04
            Reporter: Dushan Sachinda Abeyruwan
             Fix For: FUTURE
         Attachments: synapse-fix-transport.patch

  Current FIX implementation does not have a facility to read the raw fix message contexts
in origin such as in a situation like when client sends FIX raw message to JMS queue and if
that message requires to flow via ESB, and send them back to destination i.e assume another
JMS queue, so to deal in such a situation we may require a FIX message builder and formatter.

sample usage

<proxy name="FixQueue" transports="jms" startOnLoad="true" trace="disable"> 
        <target> 
            <inSequence> 
                <property name="transport.fix.ServiceName" value="FixQueue" scope="axis2-client"/>

                <log level="custom"> 
                    <property name="MESSAGE" value="FIX BINARY MESSAGE HAS BEEN RECEIVED
AND TRANFORMED"/> 
                </log> 
                <send receive="FIXResponseSequence"> 
                    <endpoint> 
                        <address uri="fix://localhost:19876?BeginString=FIX.4.0&amp;SenderCompID=SYNAPSE&amp;TargetCompID=EXEC"/>

                    </endpoint> 
                </send> 
            </inSequence> 
          </target> 
        <parameter name="transport.jms.ContentType"> 
            <rules> 
                <jmsProperty>contentType</jmsProperty> 
                <default>application/fix</default> 
            </rules> 
        </parameter> 
        <parameter name="transport.fix.DropExtraResponses">true</parameter> 
        <parameter name="transport.fix.InitiatorMessageStore">file</parameter>

        <parameter name="transport.fix.SendAllToInSequence">false</parameter>

        <parameter name="transport.fix.InitiatorConfigURL">file:repository/samples/resources/fix/synapse-sender.cfg</parameter>

    </proxy> 


  <sequence name="FIXResponseSequence"> 
        <property name="OUT_ONLY" value="true"/> 
        <log level="custom"> 
            <property name="MESSAGE" value="SENDING RESPONSE"/> 
        </log> 
        <log level="full"/> 
        <send> 
            <endpoint> 
                <address uri="jms:/FIXQueuOUT?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&amp;java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&amp;java.naming.provider.url=tcp://localhost:61616&amp;contentType=application/fix"/>

            </endpoint> 
        </send> 
    </sequence> 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


Mime
View raw message