Design validation please?

I need to keep a database in sync with a lucene index.  The database and
JVM application that updates it may be on a different machine than the
lucene index.  I was thinking that using a publish/subscribe model would
solve this problem.

Something like this;
1) Java application updates database and publishes message to jms queue
about the db update
2) Java subscribers to the queue update their lucene indexes.

While this sounds good to me, introducing JMS into the application stack
is of concern since I am already running a database, lucene indexers,
spring, hibernate, 3+ different war files as part of the techology
stack, and I am wondering if I am overengineering my idea.

I would appreciate some validation/repudiation on my idea to use open
jms in my application.

And what exact license does open jms use?

Is it possible to startup in a container like tomcat as a server, or
does it need to run as a standalone server?


Thanks for your time!




-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV