here's my jencks configuration:

 <!-- the JCA container -->
 <bean id="jencks" class="org.jencks.JCAContainer" singleton="true">

   <!-- lets use the default configuration of work manager and
transaction manager-->
   <property name="bootstrapContext">
     <bean class="org.jencks.factory.BootstrapContextFactoryBean">
       <property name="threadPoolSize" value="25"/>
     </bean>
   </property>

   <!-- the JCA Resource Adapter -->
   <property name="resourceAdapter">
     <bean id="activeMQResourceAdapter"
class="org.apache.activemq.ra.ActiveMQResourceAdapter"
singleton="true">
       <property name="serverUrl" value="tcp://localhost:61616"/>
     </bean>
   </property>
 </bean>

 <bean id="transactionManager"
class="org.jencks.factory.TransactionManagerFactoryBean"/>

 <bean id="transactionContextManager"
   class="org.jencks.factory.TransactionContextManagerFactoryBean" />

On 9/29/06, Jamie McCrindle <[EMAIL PROTECTED]> wrote:
hiya,

i'm getting a "Status is STATUS_NO_TRANSACTION" exception from
servicemix but I've just switched to using jcaFlow so I'm not too
surprised. any pointers of where to look for what might be the issue?

the setup is a webapp with an embedded servicemix container calling a
component on a standard servicemix container both using jca flow. i
suspect it's the configuration of the jca container in the webapp
that's not behaving because it's custom built but any pointers would
be awesome.

cheers,
j.

Reply via email to