This is an exported version of the JIRA issue tracker. Please use the Google Code site to open new tickets or report updates to these existing tickets. Feel free to contact the mailing list with any questions.

[SJN-50] Enable JTA transactions to work through the DataSource
Created: Wed, 28 Apr 2004 20:08:06 -0700 (PDT)  Updated: Tue, 23 Aug 2005 18:22:59 -0700 (PDT)

Status:Open
Project:Simple-JNDI
Component/s:
Affects Version/s:0.9.1
Fix Version/s:

Type:New FeaturePriority: Major
Reporter:Henri YandellAssignee:Henri Yandell
Resolution:Unresolved 
Environment:


 Description   
Request made on irc to be able to use transactions/JTA with simple-jndi.
Comment by bayard [ Sat, 1 May 2004 11:58:58 -0700 (PDT) ]
Nice as it would be to write simple-jta, for simple-jndi this really just means making it a lot easier to do factories of things.

Possibly Dave's Bunny project might have investigated how to abstract factory concepts in a persisted String based system.
Comment by bayard [ Tue, 4 May 2004 21:46:24 -0700 (PDT) ]
Add a #converter subvariable.
Possibly rename type subvariable to #type. Avoids clashes.

The #converter subvariable would specify a Converter class [interface in simple-jndi] which would have Object convert(String).

The default converter would exist and be some of the code destined to be in HierarchicalMap.

Is there a way to plug in a converter for the List that is created when a set of values are created?

Is #type compatible with other systems? Would it have the .? Seems no point. age#type age#converter.
Comment by bayard [ Tue, 4 May 2004 21:48:36 -0700 (PDT) ]
But how would this help JTA?

The type needs to be on the higher up HierarchicalMap. So:

foo.blah.url=
foo.blah.password=
foo.blah.driver=
foo.blah.user=
foo.blah#type=javax.sql.DataSource

and it is given a Map of values.

So should be possible to implement the type=DataSource as a #converter too. Hardcoded.