[ 
https://issues.apache.org/jira/browse/SYNAPSE-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232313#comment-13232313
 ] 

Dushan Sachinda Abeyruwan commented on SYNAPSE-748:
---------------------------------------------------

Hi,
 I did POC on MSMQ implementation and came up with solution, but would require 
few modifications to be done,Basically the hard part of this was the finding 
the way to implement C++ API bridge with communicate via JNI and do MSMQ 
operations as similar to what other java message brokers as Active MQ, Qupid 
does,
                So, my search mainly has focused on how C++ API can be written 
and was came up with 2 -implementations, 
                         1. i C++ API bridge developed by   
http://msmqjava.codeplex.com/SourceControl/changeset/view/48988#110283 , this 
quite a good implementation because it has functionality such as,
                              cons
                                  * a cleaner object model to handle binary or 
string messages
                                  * removal of artificial limits, like the 
128-byte limit on some messages.
                                  * improved packaging - shipped as a binary 
release, so you don't have to build it yourself.
                                  * Handle transnational messages,
                                  * Can handle binary messages
                              pros
                                    Can only handle message size upto 4 MB
                         2. And the second implementation i did transportation 
implementation based on Camel MSMQ implementation  
                                 ref links
                                       [1] http://camel.apache.org/msmq 
                                       [2] 
https://github.com/dgreco/camel-msmq/commit/732307b53cd3c9a26d6270f122294ff7e1a4d9b4
 
                                      the disadvantage if this is its handle 
minimum features such as no transaction support, and the message model is quite 
complex to understand (unless you are not a really a C++ programmer)
                     
    Even though my module is working fine for Binary messages as well as text 
messages, I do feel, still we need to enhance the feature to work  keeping SOAP 
header information in MAP, which still missing and MSMQ API has provided lesser 
detail on this how to get this done, So still this part is OPEN  and will need 
to do further search on this.

Dushan

                           

 
                
> MSMQ transport for Synapse so that Synapse can act as a MSMQ adapter
> --------------------------------------------------------------------
>
>                 Key: SYNAPSE-748
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-748
>             Project: Synapse
>          Issue Type: New Feature
>          Components: Documentation, Transports
>            Reporter: Rajika Kumarasiri
>            Priority: Minor
>              Labels: gsoc2011
>
> MSMQ is the messaging broker used by Microsoft[0]. A transport should be 
> developed which allows Apache Synapse to pick and deliver messages from/to 
> MSMQ running on Microsoft Windows. 
> The API for communicating with MSMQ available in C,C++ and C#, so a bridge 
> library also need to develop which will connect the C/C++ API to the Java 
> APIs of Apache Synapse. 
> Rajika
> [0] - http://msdn.microsoft.com/en-us/library/ms711472%28v=vs.85%29.aspx

--
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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to