cayenne-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Lindesay <>
Subject Re: Documentation
Date Thu, 13 May 2010 07:55:03 GMT

= = = = = = = = = = = 

It would be useful to have a mention and link from;


to here;


= = = = = = = = = = = 

On the page;


I am not sure what mark-up system it uses so I have left this in LaTeX for now; Ari - hope
you can transcribe this OK.  This appears to work fine, but feel free to edit it if I have
made any mistakes;

\subsection{Configuration of JMS Change Notification in a Jetty 7 Deployment with ActiveMQ}

It is assumed that the Jetty deployment has been configured to "look in" {\tt lib/ext}.  Also
assumed is that the Jetty deployment is configured to support JNDI.  Both of these configurations
can be achieved by editing the following line in the {\tt start.ini} to look something like


In this example, the messaging middleware server \href{}{ActiveMQ}
is employed.  The use of ActiveMQ assumes that the necessary client ActiveMQ driver jar files
from the ActiveMQ distribution have been installed into the {\tt lib/ext} directory in the
Jetty deployment.

In this example, the ficticious Cayenne ``Data Domain Name'' is called ``foo''.  In the Cayenne
modeller, the ``Remote Change Notifications'' is checked and the ``Connection Factory Name''
is set to;


The following would appear in the {\tt jetty.xml} file;

\begin{verbatim}<New class="">
  <New class="org.apache.activemq.ActiveMQConnectionFactory">

<New class="">
   <New class="org.apache.activemq.command.ActiveMQTopic">


That following would appear in the servlet's {\tt web.xml} file;





This configuration should enable change notification to function.

= = = = = = = = = = = 


Andrew Lindesay

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message