[jboss-user] [JBoss Seam] - Re: Problem with cache config in unit tests

[endremr]

Sorry for that missing info...

I use both unit tests where I create my components myself, but I also use FacesRequest tests where the EM's is injected automatically.

My embedded EM's are configured in "embedded-jboss-beans.xml":


  |    <bean name="NewsAdminSesamNoDSBootstrap" class="org.jboss.resource.adapter.jdbc.local.LocalTxDataSource">
  |       <property name="driverClass">org.hsqldb.jdbcDriver</property>
  |       <property name="connectionURL">jdbc:hsqldb:.</property>
  |       <property name="userName">sa</property>
  |       <property name="jndiName">java:/NewsAdminSesamNoDS</property>
  |       <property name="minSize">0</property>
  |       <property name="maxSize">10</property>
  |       <property name="blockingTimeout">1000</property>
  |       <property name="idleTimeout">100000</property>
  |       <property name="transactionManager"><inject bean="TransactionManager"/></property>
  |       <property name="cachedConnectionManager"><inject bean="CachedConnectionManager"/></property>
  |       <property name="initialContextProperties"><inject bean="InitialContextProperties"/></property>
  |    </bean>
  | 
  |    <bean name="NewsAdminSesamNoDS" class="java.lang.Object">
  |       <constructor factoryMethod="getDatasource">
  |          <factory bean="NewsAdminSesamNoDSBootstrap"/>
  |       </constructor>
  |    </bean>
  | 

I thought that this was the thing that created my entity managers, but the properties in "persistence.xml" is also used, and this triggers the tree cache connection.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100565#4100565

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4100565