Announcement Announcement Module
Collapse
No announcement yet.
Weblogic JMS Wrappers and J2EE Compliance Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Weblogic JMS Wrappers and J2EE Compliance

    Hi,

    We're looking to use a Weblogic J2EE wrapper for a JMS ConnectionFactory we look up via a JndiObjectFactoryBean. We are looking to do this in order to get some of the benefits of using a ConnectionFactory Weblogic wrapper - such as pooling, fault tolerance etc.

    Wiring up the ConnectionFactory in the web.xml/weblogic.xml and referencing that in the Spring configuration is fairly straightfoward - as documented here:

    http://edocs.bea.com/wls/docs92/jms/j2ee.html

    The issue we have, is that the wrapped ConnectionFactory (and objects it creates) enforce J2EE compliance by ensuring that disallowed JMS API calls throw an exception - as the J2EE spec says that certain API calls cannot be made inside a J2EE application.

    An example is setting the message listener on the message consumer object - but the Spring MessageListenerContainer we're using attempts to call setListener() on the message consumer - and thus triggers one of these exceptions.

    Is there any way around this? At the moment, we're doing a direct JNDI lookup of the ConnectionFactory (outside the scope of the deployment descriptors) meaning we don't get a wrapped ConnectionFactory and therefore no compliance exceptions.

    Thanks in advance,

    Will
Working...
X