David Jencks wrote:
I think there are several related issues here... I hope I'm not confusing
things further.
1. I think we agree on vendor specific ManagedConnectionFactory
implementations wrapping vendors' XADataSource implementations, with
customized XAResource wrappers.
More or less.
On 2002.08.29 08:10:08 -0400 Igor Fedorenko wrote:
David Jencks wrote:
I think there are several related issues here... I hope I'm not
confusing
things further.
1. I think we agree on vendor specific ManagedConnectionFactory
implementations wrapping vendors' XADataSource
I have checked in my changes -- fixed XAManagedConnectionFactory,
DataSourceTemplate.xsl as well as example oracle-xa-ds.xml. I decided
not to implement oracle specific mcf now but may reconsider it later. I
also renamed *.java files with preprocessor markup into *.jpp.
David Jencks wrote:
Thanks! This looks good. Do you have Oracle working with the new xa
wrapper?
david jencks
On 2002.08.29 16:51:45 -0400 Igor Fedorenko wrote:
I have checked in my changes -- fixed XAManagedConnectionFactory,
DataSourceTemplate.xsl as well as example oracle-xa-ds.xml. I decided
not to
David Jencks wrote:
Thanks! This looks good. Do you have Oracle working with the new xa
wrapper?
Sort of. It deploys datasource and runs very simple test (one ssb calls
another, both beans get connection and insert data into the db).
I would cleanup BaseWrapperManagedConnectionFactory and
On 2002.08.29 18:05:08 -0400 Igor Fedorenko wrote:
David Jencks wrote:
Thanks! This looks good. Do you have Oracle working with the new xa
wrapper?
Sort of. It deploys datasource and runs very simple test (one ssb calls
another, both beans get connection and insert data into the db).
David Jencks wrote:
In all but basic configurations the user/pw should be coming from a JAAS
login module. Setting the user/pw on the mcf properties should be a last
resort for when you can't get user/pw anywhere else.
Agreed, but it is extreemly convinient during testing. ;-)
We need a
On 2002.08.27 09:19:04 -0400 Igor Fedorenko wrote:
David Jencks wrote:
In all but basic configurations the user/pw should be coming from a
JAAS
login module. Setting the user/pw on the mcf properties should be a
last
resort for when you can't get user/pw anywhere else.
Agreed, but it
David Jencks wrote:
On 2002.08.27 09:19:04 -0400 Igor Fedorenko wrote:
[skipped]
How do I deploy rm specific wrapper? Am I right that there is a
prototype RARDeployment instance
(jboss.jca:service=RARDeployment,name=JBoss JDBC XATransaction
ResourceAdapter) that defines wrapper to be
I think there are several related issues here... I hope I'm not confusing
things further.
1. I think we agree on vendor specific ManagedConnectionFactory
implementations wrapping vendors' XADataSource implementations, with
customized XAResource wrappers.
2. It is not really essential for
Hi guys,
Currently we have single set of properties that are passed from
RARDeployer down to jdbc.xa.XAManagedConnectionFactory. This single set
is used in two places. First, when xa datasource is being initialized
the properties are used to set attributes of the datasource (exception
is
11 matches
Mail list logo
