On Mon, May 19, 2008 at 3:23 PM, Andreas Veithen <[EMAIL PROTECTED]> wrote:
> Senaka, > > Please see my comments inline. > > Andreas > > On 17 May 2008, at 07:54, Senaka Fernando wrote: > > Hi devs, >> >> In the Synapse JMS Transport, we don't support MapMessage as yet, even >> though it was discussed some two years back. Mainly this is due to it >> being much un-popular I believe. >> >> We are working on the Synapse-Esper Mediation these days, and it is >> crucial to have JMS Map Message support in order to improve the efficiency >> of the Synapse JMS Transport, so that a user utilizing EsperIO and Esper >> should get the same experience (or better) with Synapse and Esper. >> >> After discussing with Paul, it also seems better to have an implementation >> of org.apache.axiom.om.OMDataSourceExt so that we'll be capable of having >> a Map-Backed-OMElement. Thus, through a wrapper we'll be capable of >> mapping the MapMessage to a java.util.Map object that will be stored >> within the OMElement. >> >> > Why MapMessage->java.util.Map->OMDataSourceExt and not > MapMessage->OMDataSourceExt? > > Where do you see the added value of using an OMDataSourceExt instead of > simply transforming the MapMessage into an AXIOM tree? > I think MapMsg -> Map -> AXIOM on demand is the most efficient way. For a JMS only loop or if you are using non XML mediators (ex Java mediator) it is sub optimal to convert to XML. So we could just keep it as a Map and convert it to AXIOM when we need it (and then cache that for any subsequent use). > > > Therefore, having both of these in mind, we would like to know your >> thoughts on the best approach that we could take. >> >> The current major concerns are, >> >> 1. How to convert the MapMessage into an XML Representation? >> >> > You will have to define a mapping between MapMessage and XML. It should be > chosen such that the XML representation can be easily manipulated with XPath > expressions, XSLT transforms and scripts. > > 2. How should the get/set Property methods in OMDataSourceExt be >> implemented? are we going to use the same Map, or have another HashMap? >> >> > The question is actually: what is the meaning of > OMDataSourceExt#(get|set)Property? The Javadoc doesn't tell anything and I > could only find a single piece of code that uses these methods, namely > SOAPHeaderBlock. In this case the properties are used as some kind of > pseudo-attributes. Did you have a closer look at this question? > > > Regards, >> Senaka >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/
