[
https://issues.jboss.org/browse/WFLY-9092?page=com.atlassian.jira.plugin....
]
Brad Maxwell commented on WFLY-9092:
------------------------------------
Prior to JBoss AS 7 / Wildfly it was possible, but never recommended:
- It is not a good idea to have an unreliable client directly controlling the resources of
your server (i.e. JDBC connections).
- If the client loses network connectivity or crashes before it is able to close the
connection then the connection will not be closed until the server is shutdown (i.e. it
will be leaked).
- It is very slow. All database operations are proxied through an MBean.
- Transaction propagation is not supported.
It recommend using an EJB as an intermediary in accessing the data source, and defining a
proper contract for how the data should be accessed and operated on.
Access jndi datasource outside eap container?
---------------------------------------------
Key: WFLY-9092
URL:
https://issues.jboss.org/browse/WFLY-9092
Project: WildFly
Issue Type: Feature Request
Components: EE, JCA
Reporter: harit kumar
Access jndi datasource outside eap container?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)