I would appreciate the work, and as a team member I'd be honored that you would think to put this under the iBATIS umbrella.
However, I think it's such a diversion from the central purpose of iBATIS that it would threaten to blur what iBATIS is. I would rather see it as a fork. Forks aren't bad when they're doing something completely different. They're only bad when they do exactly the same thing so as to confuse the meaning of the framework. A LDAP or TIBCO data mapping framework would clearly be differentiated from a JDBC framework. Just my initial thoughts... Clinton On 1/2/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
The team I work on is currently using iBatis for Java for all of our JDBC data access with great results, and having found the benefits of it, we are now working towards a data access solution that has a slightly larger scope than iBatis, but wit the same benefits and general philosophy. Specifically we need to retrieve data not only from JDBC sources, but also from other sources such as TIBCO and , LDAP. We are looking to have the same ease of use and power of iBatis with these sources, and will be doing all of the development and testing to accomplish this. What we really do not want to do however is try to fork the project. so we are faced with either building functionality similar to iBatis for the other sources, our strong preference extending iBatis to handle these sources. For reviewing the source code, the primary outward change would be to create additional parallel methods using a more abstract iBatis specific class or interface in place of Connection and SQLException. Obviously the internal changes would need to be more involved. Were this development completed and offered as a contribution, what is the current feeling on how well it would be received? Many thanks in advanced..... --------------------------------------------------------------------- This message, together with any attachments, is intended only for the use of the individual or entity to which it is addressed. It may contain information that is confidential and prohibited from disclosure. If you are not the intended recipient, you are hereby notified that any dissemination or copying of this message or any attachment is strictly prohibited. If you have received this message in error, please notify the original sender immediately by telephone or by return e-mail and delete this message, along with any attachments, from your computer. Thank you. ---------------------------------------------------------------------
