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 xa wrapper for each xadatasource that exposes its exact > properties and compensates for its non-spec-compliance. These are now very > easy to write, lets not make some general purpose 10000 line adapter that > tries and fails to be all things to all adapters. > > Please, write an Oracle specific wrapper rather than try to generalize the > base xa wrapper. Setting all the mcf properties at once is a dreadful hack > caused mostly by my not having any XADataSources to work with. 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 used? Should I deploy such prototype for each resource manager or it is better to get rid of prototype and provide all necesary info in -ds.xml? > > david jencks > > On 2002.08.27 00:30:39 -0400 Igor Fedorenko wrote: > >>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 thrown, if a propety does not have corresponding attribute). Second, >>when xa connection is created we use same properties to get username and >>password for new connection, this is done using specific property names >>"user" and "password". Obviously, if datasource does not have "user" >>and/or "password" attribute there is no way we can pass those two >>parameters to XADataSource.getXAConnection(String, String) call. >> >>Possible solution would be to use special naming convention for "user" >>and "password" properties (like "XADataSource:user" or something that >>cannot be confused with attribute name). When we initialize a datasource >>we ignore such special properties. >> >>Thoughts? >> >>-- >>Igor Fedorenko >>Think smart. Think automated. Think Dynamics. >>www.thinkdynamics.com >> >> >> >>------------------------------------------------------- >>This sf.net email is sponsored by: OSDN - Tired of that same old >>cell phone? Get a new here for FREE! >>https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 >>_______________________________________________ >>Jboss-development mailing list >>[EMAIL PROTECTED] >>https://lists.sourceforge.net/lists/listinfo/jboss-development >> >> > > > > ------------------------------------------------------- > This sf.net email is sponsored by: OSDN - Tired of that same old > cell phone? Get a new here for FREE! > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development -- Igor Fedorenko Think smart. Think automated. Think Dynamics. www.thinkdynamics.com ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
