The real question is whether SWIFT is an application layer protocol (like HTTP) or just a content exchange format (like XML). You should probably look into the SWIFT specification and figure out an answer to this question. The type of implementation required depends on the answer. If it is an application layer protocol then we need a transport. But if it's just a content exchange format that runs on existing application layer protocols, we only need a message builder and a formatter.
It's also possible that we need both. HL7 is a good example to such a scenario. HL7 integration requires supporting an application layer protocol known an SMPP. But it can also work on existing protocols such as HTTP by leveraging HL7 message formats. So we need a transport as well as a builder/formatter in that case. Perhaps SWIFT also falls into that category. Let us know what you can find out from the SWIFT specs. Thanks, Hiranya On May 5, 2013, at 9:12 PM, Chaamini Mangaleswaran <[email protected]> wrote: > Hi All, > > I am trying to develop a new feature for Apache Synapse to support SWIFT > Protocol. As the initial step I am trying to use the JMS transport already > available and build a message builder and message formatter, which can > convert SWIFT messages to XML and vice versa. For this conversion I am trying > to use the open source SWIFT message management framework called WIFE. > But there is another approach to implement it as a standalone transport > protocol by using Apache Mina and a transport sender and receiver. Will the > first approach will be sufficient to meet the requirement ?I would like to > hear your thoughts on this idea! > > > > > Thanks & Regards, > Chaamini > > Keep Smiling ! -- Hiranya Jayathilaka Mayhem Lab/RACE Lab; Dept. of Computer Science, UCSB; http://cs.ucsb.edu E-mail: [email protected]; Mobile: +1 (805) 895-7443 Blog: http://techfeast-hiranya.blogspot.com
