I personally think that a STOMP client should request a transformation strategy. For example on a subscribe, he could do
SUBSCRIBE destination: /queue/foo transformation: jms-json ack: client And on the reverse side, The send could look like: SEND destination:/queue/a transformation: jms-json ["Hello World",1] ^@ And have the Stomp transport handle those "transformation" headers by looking up the "jms-json" transformation in the spring context. This would allow the broker to have extensible transformations. And the looked up object would just need to implement the following interface: http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/transport/stomp/FrameTranslator.html Just need to find someone who is willing to take a stab at enhancing the stomp transport so that it does those "transfromation" header handling logic. And add a few more interesting implementations of FrameTranslator. Regards, Hiram On Dec 14, 2007 6:54 AM, Dejan Bosanac <[EMAIL PROTECTED]> wrote: > And now to continue :) .... sorry about this ... > > > > I was thinking recently if there should be a configurable support for > > message transforming on the broker level. For example, one use case > > would be to do XML/Object transformation of all messages > > received/transmitted through the Stomp protocol. > > I guess now that Camel is integrated in AMQ it could be achieved > through message translators > > http://activemq.apache.org/camel/message-translator.html > > but maybe a support for some kind of transport listeners, could be > handy in these kind of situations. > > The client-side transformers could not be used since they are tied to > consumers/produces but some sort of lightweight interface for this > purpose could be provided. > > To me it seems that transport listeners are the place where this can > be done easily, but someone with more experience with AMQ architecture > could provide a better suggestion (of course if it is worth doing it > at all). > > > Cheers > -- > Dejan Bosanac > www.scriptinginjava.net > > > On Dec 14, 2007 12:46 PM, Dejan Bosanac <[EMAIL PROTECTED]> wrote: > > I was thinking recently if there should be a configurable support for > > message transforming on the broker level. For example, one use case > > would be to do XML/Object transformation of all messages > > received/transmitted through the Stomp protocol. I guess now that > > Camel is integrated in AMQ > > > > -- > > Dejan Bosanac > > www.scriptinginjava.net > > > -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://open.iona.com
