Man, all these layers upon other layers and their configuration... it's a bit 
overwhelming. Anyway, the jboss-beans.xml (the name of this file implied to me 
that the db connection was managed by the microcontainer by the way) is an 
adaptation of the one in the JPA example:


  | <?xml version="1.0" encoding="UTF-8"?>
  | 
  | <deployment xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
  |             xsi:schemaLocation="urn:jboss:bean-deployer 
bean-deployer_1_0.xsd"
  |             xmlns="urn:jboss:bean-deployer">
  |             
  |   <bean name="Naming" class="org.jnp.server.SingletonNamingServer"/>
  | 
  |   <bean name="TransactionManagerFactory" 
  |     class="org.jboss.seam.microcontainer.TransactionManagerFactory"/>
  |   <bean name="TransactionManager" class="java.lang.Object">
  |     <constructor factoryMethod="getTransactionManager">
  |       <factory bean="TransactionManagerFactory"/>
  |     </constructor>
  |   </bean>
  | 
  |   <bean name="bookingDatasourceFactory" 
  |        class="org.jboss.seam.microcontainer.DataSourceFactory">
  |     <property name="driverClass">org.hsqldb.jdbcDriver</property>
  |     <property name="connectionUrl">jdbc:hsqldb:testing</property>
  |     <property name="userName">sa</property>
  |     <property name="jndiName">java:/DefaultDS</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>
  |   </bean>
  |   <bean name="bookingDatasource" class="java.lang.Object">
  |     <constructor factoryMethod="getDataSource">
  |       <factory bean="bookingDatasourceFactory"/>
  |     </constructor>
  |   </bean>
  | 
  | </deployment>
  | 

I guess this creates the in-memory variant of the HSQL database? So far I've 
only connected to file-based ones. Using the string jdbc:hsqldb:testing in 
HSQLDBManager does connect, but shows an empty DB (though the schema export 
allegedly succeeded). Furthermore,  changing testing to any arbitrary name 
leads to a succesful connection, that's suspicious...


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

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4036283
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to