I don't think we need an additional parameter to identify the lazy
initializations. Because if the session not defined in the
synapse.initiator config (pointed by transport.fix.InitiatorConfigURL)
system will create the session on the fly when message arrives. So it is
an lazy initialization.
Asanka A.
Hiranya Jayathilaka (JIRA) wrote:
[ https://issues.apache.org/jira/browse/SYNAPSE-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611903#action_12611903 ]
Hiranya Jayathilaka commented on SYNAPSE-380:
---------------------------------------------
We can ask the user to put all the settings required to create the session with the acceptor in the file pointed to by the transport.fix.InitiatorConfigURL parameter. Then we can modify the existing FIX transport impl to check for this parameter at startup and create the session if all the required settings are specified in the file.
I'm also planning to introduce a new service parameter
(transport.fix.LazyInitSessions) which when set to 'on' will cause Synapse to
create sessions with the acceptors only when a message arrives for that
sessions (ie the existing way of creating sessions)
Create/initiate the FIX session with the acceptor endpoint in the startup of
Synapase
-------------------------------------------------------------------------------------
Key: SYNAPSE-380
URL: https://issues.apache.org/jira/browse/SYNAPSE-380
Project: Synapse
Issue Type: Improvement
Components: Transports
Affects Versions: 1.2
Environment: Java 1.5,
Reporter: Asanka Abeysinghe
Assignee: Hiranya Jayathilaka
Initiate the FIX session with the acceptor endpoint(s) defined in the synapse
configuration and connect immediately if the endpoint is up or connect when the
endpoint starts up.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
