Hi Andrew,WebObjects is clever because it uses the standard EOModel database connection in development and then when you deploy (and resource-ref/resource-ref is uncommented in web.xml.template) EOF ignores the EOModel connection string and automatically uses the jboss data source connection which
We are using jboss 4. We are letting jboss handle the connections
using the jndi by putting a datasource xml file in the deployment
directory (in our case postgres-ds.xml) that was referenced from
jboss-web.xml
D Tim Cummings
On 29/06/2006, at 03:40, David Aspinall wrote:
We are not
Hi,is anyone deploying their webobjects peoject withing Jboss 4.0.x? If so, how are you handling your DB connections, are you letting Jboss handle the connection via JNDI or are you letting webojects handle it?
thanks in advanceAndrew
___
Do not post
We are not using JBoss, but we are using WebSphere and all database
connections are handled by the IBM Connection pool. We got all kinds
of connection issues (incomplete transactions, deadlocks, closed
connections) because EOF like to make a connection and hold it forever.
To fix it i
