Hi, Thank you for the very fast response.
So if I understand it correctly and please correct me if I am wrong: When a document is published/created/updated/deleted, the document state changes. And because of the document state has changed a JMS message is sent to the queue. However the JMS message does not state what event actually happens. Hence based on the generated message you can not identify what actually happened to the document. As the document might just have been updated, created or deleted. Best regards Ricardo > Date: Tue, 4 Nov 2008 15:29:59 +0100 > From: [EMAIL PROTECTED] > To: [email protected] > Subject: Re: [HippoCMS-dev] FW: JMS queue of Hippo > > On Tue, Nov 04, 2008 at 03:06:48PM +0100, Ricardo Sawirjo wrote: > > Hi, I want to listen to the JMS queue of Hippo in case something is > > published from within the Hippo CMS.Can you provide me with information how > > to do this? What is for example the JNDI name of the queue?Do I need to > > subscribe first to the queue for a specific topic? In case there are topics > > to subscribe to, what topics are there available to subscribe to? Hopefully > > you can provide me with some answers. Best regards Ricardo > > Events like publishing a document are not explicitly send as messages over > the JMS system. The publication of a document is an action inside of the CMS > itself. It does however update the published document (as it is being > copied over to the live state). Updates, creations and deletion of documents > are reported by the repository over JMS. It is therefor indirectly that > you are able to trap such events, however it is not evident which type of > event triggers this through JMS. > > The JMS Topics are defined in the components.xconf file in the configuration > of the repository. Look for a section defining: > <jms-connection-manager id="jms-connection-manager" logger="jms.manager"> > <topic-connection name="local-topics"> > ... > <parameter name="connection-factory" value="jms/repositoryTCF"/> > ... > </topic-connection> > </jms-connection-manager> > and > <index-jms-notification-trigger id="index-jms-notification-trigger" > logger="slide.notification"> > ... > <parameter name="topic" value="jms/repositoryTopic"/> > </index-jms-notification-trigger> > > which define the Topic connection (jms/repositoryTCF) and Topic > (jms/repositoryTopic) to listen for. The events are SlideEvent classes > if I remember correctly. > > \Berry > -- > Berry A.W. van Halderen [EMAIL PROTECTED] / [EMAIL PROTECTED] > Disclaimer: the above is the author's personal opinion and is not the opinion > or policy of his employer or of the little green men that have been following > him all day. > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > > Searchable archives can be found at: > MarkMail: http://hippocms-dev.markmail.org > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html > _________________________________________________________________ Zoek en win prachtige prijzen met Lucky Search! http://www.luckysearch.nl/******************************************** Hippocms-dev: Hippo CMS development public mailinglist Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
