[
https://issues.jboss.org/browse/JBJCA-1112?page=com.atlassian.jira.plugin...
]
Jesper Pedersen commented on JBJCA-1112:
----------------------------------------
A DataSource isn't serializable, but the JCA connection factory, which in this case
represents the DataSource instance, has to be.
Ideally the JCA connection manager has to be serializable too, but IronJacamar 1.x
doesn't implement this contract, since it isn't trivial - f.ex. there can't be
any active connections.
I'll see if I can find a hack at the JDBC resource adapter level in order to work
around this issue. A workaround could be to don't serialize JCA backed resources, and
reinject them again during readObject().
DataSource marked as Serializable
---------------------------------
Key: JBJCA-1112
URL:
https://issues.jboss.org/browse/JBJCA-1112
Project: IronJacamar
Issue Type: Bug
Components: Deployer, JDBC
Affects Versions: 1.0.21.Final, 1.1.1.Final
Reporter: Paul Ferraro
Assignee: Jesper Pedersen
Priority: Critical
Fix For: 1.0.23.Final, 1.1.2.Final
See JBPAPP6-1762 for details.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira