On 6/6/07, Raffaele <[EMAIL PROTECTED]> wrote:
I'm making a sort of wrapping of some of the main classes of ActiveMQ, in detail i have: - JMSWorker - QueueWorker extends JMSWorker - TopicWorker extends JMSWorker - QueueBrowser extends QueueWorker - QueueConsumer extends QueueWorker - QueueProducer extends QueueWorker - TopicConsumer extends TopicWorker - TopicPublisher extends TopicWorker This wrapping permits me to abstract my code from the JMS implementation, in fact till now I used Oracle JMS implementation and so, passing from Oracle to ActiveMQ should be as trasparent as possible using the above wrapper classes.
FWIW the purpose of the JMS API is to do exactly that, to avoid having your code dependent on any particulary JMS provider. If you want an easier facade on top of the JMS API I'd recommend either the Spring JMS stuff, or Camel http://activemq.apache.org/camel/ In particular http://activemq.apache.org/camel/enterprise-integration-patterns.html -- James ------- http://macstrac.blogspot.com/
