lots of the information in the advisories is stored in properties and these properties are not automatically mapped into the stomp message so most of the information in the advisory is lost when it is consumed via stomp. It may be an easy enough fix if you are interested to have a go at a resolution.
On 21 May 2010 11:01, Markus Schaber <m...@soloplan.de> wrote: > > Hi, Dejan, > > > Dejan Bosanac wrote: > > > > the most natural way would be to use advisory messages ( > > http://activemq.apache.org/advisory-message.html), but this is not yet > > supported from Stomp (https://issues.apache.org/activemq/browse/AMQ-2098 > ), > > so you'd need to use Java to process this kind of events. > > > > Just to double-check whether I understand this issue correctly: The > advisory > messages are genereated for clients connecting via Stomp, but it currently > is not possible to receive those mesages via Stomp? > > Thanks, > Markus > -- > View this message in context: > http://old.nabble.com/Finding-out-when-client-is-offlin-tp28594744p28631844.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source Integration http://fusesource.com
