This should be pretty easy to do starting from the local tx jdbc wrapper. Here's what I think you need to do:
0. Copy all the files and change the package and file names, change the interface for LocalDataSource to something more suitable. 1. Remove the Statement, PreparedStatement, and CallableStatement wrappers. 2. Remove all the transaction related code from the Connection wrapper and ManagedConnection implementation. 3. Replace the jdbc interface implemented by the Connection wrapper with the appropriate LDAP interface, so your Connection object wraps a LDAP connection. Be sure that which LDAP connection is used can be changed by the ManagedConnection.associateConnection method. 4. Replace the code that gets a jdbc Connection in the ManagedConnection constructor with code that gets an LDAP connection. 5. Figure out how to map a Subject supplied by the app server to whatever security info the LDAP stuff needs, and implement it in the ManagedConnection constructor or helper methods. 6. Read through the rest of the code eliminating what doesn't apply. For a first draft at least you probably don't need to wrap any Statement-like objects returned from the Connection. david jencks On 2002.06.22 21:54:09 -0400 David Jencks wrote: > I'd like to encourage you to contribute it to jboss. I'll be happy to > give > advice and code reviews. You can probably get jboss cvs commit access a > little way into the project, after a couple of code submissions, > meanwhile > I can commit things for you. > > If you decide to contribute to jboss, please put it in a package like > > org.jboss.resource.adapter.ldap > > so it will fit in with the others we have. > > Thanks! > > david jencks > > On 2002.06.22 21:26:56 -0400 Elizabeth Barham wrote: > > Hi Keene, > > > > "Keene Hammond" <[EMAIL PROTECTED]> writes: > > > > > Elizabeth, > > > First, my apologies for jumping in to the middle of a discussion. > > But... > > > How far have you gone into writing this adapter? > > > > I managed to download the connector specs from sun! ;-) > > > > > I have experimented using BMP and was successful at creating a bean > > > but I found that is was unwieldy and was not really reusable (not > > > the kind of code I like to use). I have also tried using the > > > External JNDI namespace but found that it lacks the robustness that > > > I require. > > > > > I have been using a CustomMBean that wraps up the > > > netscape.ldap.util.ConnectionPool for pooling in my JBoss 2.4.X > > > server but I have found that it does not fit well with JBoss 3.X. > > > > > I need this type of adapter and would be interested in helping to > > > create, or creating such an apdapter for the JBoss user community. > > > > Perhaps we should make a sourceforge project? > > > > Elizabeth > > > > > > ------------------------------------------------------- > > Sponsored by: > > ThinkGeek at http://www.ThinkGeek.com/ > > _______________________________________________ > > JBoss-user mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > > > > ------------------------------------------------------- > Sponsored by: > ThinkGeek at http://www.ThinkGeek.com/ > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > ------------------------------------------------------- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
