Hi Claus,
this bean is configured like this:
<bean id="ibmmqvsl"
class="org.apache.camel.component.jms.JmsComponent">
<property name="connectionFactory" ref="jmshostcf" />
<property name="transactionManager" ref="txman" />
</bean>
<jee:jndi-lookup id="jmshostcf" jndi-name="java:comp/env/jms/vslmqmgr"
cache="true" />
<bean id="txman"
class="org.springframework.transaction.jta.WebSphereUowTransactionManager"
/>
<jee:jndi-lookup id="zifsdb" jndi-name="java:comp/env/jdbc/ZIFSDB" />
And the JNDI-lookup looks up a WMQ-Connection Factory configured in
WebSphere AS.
Maybe this is of interest or not, but i have a @ManagedResource - JMX-Bean,
that's called from a simple Jar from outside of WebSphere. And this
JMX-MBean has the Camelcontext injected from Spring.
Maybe that context has sth to do with it, because actually the above
configuration is used by other Routes that work. But those routes get
started from an incoming message from the messagebroker, meaning the context
(of route starting) stays within itself.
Claus Ibsen-2 wrote:
>
> Hi
>
> How have you configured this bean, ibmmqvsl ?
>
>
>
>
--
View this message in context:
http://old.nabble.com/Method-setExceptionListener-not-permitted-in-J2EE-Servers-tp28693246p28727346.html
Sent from the Camel - Users mailing list archive at Nabble.com.
