Why do you object to serializing the endpoint? Seems like it would be the right thing to do. Can't it be serialized as a <wsa:to> address in the message header?
Paul On Sun, Aug 1, 2010 at 7:24 AM, Charith Wickramarachchi <[email protected]> wrote: > Hi devs , > While working on the patch for the JMS Based Message store i got stuck in > the place where i need to persist the Message. > Idea of persisting message is to later it can be redelivered or views later. > So in the InMemory Message store case when storing i kept the reference to > the Message context (built) and its associated endpoint. > Keeping a reference to the Endpoint in this case is not costly since its > just an Object reference. > But keeping the Endpoint associated with a Message Context is > bit problematic in a persistent scenario since there is no point > in serializing the Endpoint :). > I have 2 solutions to solve this. > > Make all the endpoints globally accessible from the configuration (Even > the anonymous ones Ex : say a endpoint defined in a send mediator). so that > i need only to keep the name of the endpoint with the Message. > Support Message store feature only with the Endpoints defined globally. > > WDYT ? > > -- > Charith Dhanushka Wickramarachchi > http://charithwiki.blogspot.com/ > > -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [email protected] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
