[jira] Updated: (GERONIMO-889) Replace Geronimo-Derby-Connector with TranQL Vendors Derby Connector

2005-08-26 Thread Matt Hogstrom (JIRA)
 [ http://issues.apache.org/jira/browse/GERONIMO-889?page=all ]

Matt Hogstrom updated GERONIMO-889:
---

Attachment: geronimo0826.diff

Updated with current patches.

 Replace Geronimo-Derby-Connector with TranQL Vendors Derby Connector
 

  Key: GERONIMO-889
  URL: http://issues.apache.org/jira/browse/GERONIMO-889
  Project: Geronimo
 Type: Improvement
  Environment: All
 Reporter: Matt Hogstrom
  Attachments: geronimo.patch, geronimo0826.diff, openejb.patch, 
 openejb0826.diff

 TranQL AbstractConnectorMCF has been updated to conform to the JCA 1.5 
 specification.  As such the current DerbyConnector no longer compiles due to 
 method changes on set/getLoginTimeout.  There were two choices to be made 
 here.  Modify the Derby-Connector or replace the connector.  TranQL provides 
 a set of connectors for multiple vendors (Oracle and Derby currently with DB2 
 coming before V1 of Geronimo) which provides the same functionality as the 
 Derby-Connector along with additional database vendor support.
 I have spoken with Dave Jencks and Jeremy about the change and we think this 
 is the best way to proceed.
 I don't know what appliacations may be relying 
 If we agree to make this change this improvement does the following:
 1. Updates all artifacts in the current Geronimo Build to include the TranQL 
 Vendors connectors and remove all references to the Geronimo-Derby-Connector.
 2. Updates OpenEJB to pull the correct version of the TranQL connector
 3. Updates the sandbox PetStore Project to pull in the new connector as well.
 4. Console Update to change the connector class (imbedded as a string in one 
 of the portlets.
 I am finishing the patches to update the various components and testing them 
 out.  Given the magnitude of the change (updating multiple projects) I wanted 
 to get this out for discussion now.  Patches should be ready in a day or so 
 after I've verified them.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[jira] Updated: (GERONIMO-889) Replace Geronimo-Derby-Connector with TranQL Vendors Derby Connector

2005-08-26 Thread Matt Hogstrom (JIRA)
 [ http://issues.apache.org/jira/browse/GERONIMO-889?page=all ]

Matt Hogstrom updated GERONIMO-889:
---

Attachment: geronimo0826a.diff
openejb0826a.diff
geronimo0826.diff

Reposting files.  Forgot to grant ASF license.

0826 and 0826a files both need to be applied.  

m:rebuild-all, tests and itests now  pass.

 Replace Geronimo-Derby-Connector with TranQL Vendors Derby Connector
 

  Key: GERONIMO-889
  URL: http://issues.apache.org/jira/browse/GERONIMO-889
  Project: Geronimo
 Type: Improvement
  Environment: All
 Reporter: Matt Hogstrom
  Attachments: geronimo.patch, geronimo0826.diff, geronimo0826.diff, 
 geronimo0826a.diff, openejb.patch, openejb0826.diff, openejb0826a.diff

 TranQL AbstractConnectorMCF has been updated to conform to the JCA 1.5 
 specification.  As such the current DerbyConnector no longer compiles due to 
 method changes on set/getLoginTimeout.  There were two choices to be made 
 here.  Modify the Derby-Connector or replace the connector.  TranQL provides 
 a set of connectors for multiple vendors (Oracle and Derby currently with DB2 
 coming before V1 of Geronimo) which provides the same functionality as the 
 Derby-Connector along with additional database vendor support.
 I have spoken with Dave Jencks and Jeremy about the change and we think this 
 is the best way to proceed.
 I don't know what appliacations may be relying 
 If we agree to make this change this improvement does the following:
 1. Updates all artifacts in the current Geronimo Build to include the TranQL 
 Vendors connectors and remove all references to the Geronimo-Derby-Connector.
 2. Updates OpenEJB to pull the correct version of the TranQL connector
 3. Updates the sandbox PetStore Project to pull in the new connector as well.
 4. Console Update to change the connector class (imbedded as a string in one 
 of the portlets.
 I am finishing the patches to update the various components and testing them 
 out.  Given the magnitude of the change (updating multiple projects) I wanted 
 to get this out for discussion now.  Patches should be ready in a day or so 
 after I've verified them.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[jira] Updated: (GERONIMO-889) Replace Geronimo-Derby-Connector with TranQL Vendors Derby Connector

2005-08-26 Thread Matt Hogstrom (JIRA)
 [ http://issues.apache.org/jira/browse/GERONIMO-889?page=all ]

Matt Hogstrom updated GERONIMO-889:
---

Attachment: openejb0826a.diff

Maven and project file updates for new connector.

 Replace Geronimo-Derby-Connector with TranQL Vendors Derby Connector
 

  Key: GERONIMO-889
  URL: http://issues.apache.org/jira/browse/GERONIMO-889
  Project: Geronimo
 Type: Improvement
  Environment: All
 Reporter: Matt Hogstrom
  Attachments: geronimo.patch, geronimo0826.diff, geronimo0826.diff, 
 geronimo0826a.diff, openejb.patch, openejb0826.diff, openejb0826a.diff, 
 openejb0826a.diff

 TranQL AbstractConnectorMCF has been updated to conform to the JCA 1.5 
 specification.  As such the current DerbyConnector no longer compiles due to 
 method changes on set/getLoginTimeout.  There were two choices to be made 
 here.  Modify the Derby-Connector or replace the connector.  TranQL provides 
 a set of connectors for multiple vendors (Oracle and Derby currently with DB2 
 coming before V1 of Geronimo) which provides the same functionality as the 
 Derby-Connector along with additional database vendor support.
 I have spoken with Dave Jencks and Jeremy about the change and we think this 
 is the best way to proceed.
 I don't know what appliacations may be relying 
 If we agree to make this change this improvement does the following:
 1. Updates all artifacts in the current Geronimo Build to include the TranQL 
 Vendors connectors and remove all references to the Geronimo-Derby-Connector.
 2. Updates OpenEJB to pull the correct version of the TranQL connector
 3. Updates the sandbox PetStore Project to pull in the new connector as well.
 4. Console Update to change the connector class (imbedded as a string in one 
 of the portlets.
 I am finishing the patches to update the various components and testing them 
 out.  Given the magnitude of the change (updating multiple projects) I wanted 
 to get this out for discussion now.  Patches should be ready in a day or so 
 after I've verified them.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[jira] Updated: (GERONIMO-889) Replace Geronimo-Derby-Connector with TranQL Vendors Derby Connector

2005-08-19 Thread Matt Hogstrom (JIRA)
 [ http://issues.apache.org/jira/browse/GERONIMO-889?page=all ]

Matt Hogstrom updated GERONIMO-889:
---

Attachment: openejb.patch

Patches for OpenEJB

 Replace Geronimo-Derby-Connector with TranQL Vendors Derby Connector
 

  Key: GERONIMO-889
  URL: http://issues.apache.org/jira/browse/GERONIMO-889
  Project: Geronimo
 Type: Improvement
  Environment: All
 Reporter: Matt Hogstrom
  Attachments: geronimo.patch, openejb.patch

 TranQL AbstractConnectorMCF has been updated to conform to the JCA 1.5 
 specification.  As such the current DerbyConnector no longer compiles due to 
 method changes on set/getLoginTimeout.  There were two choices to be made 
 here.  Modify the Derby-Connector or replace the connector.  TranQL provides 
 a set of connectors for multiple vendors (Oracle and Derby currently with DB2 
 coming before V1 of Geronimo) which provides the same functionality as the 
 Derby-Connector along with additional database vendor support.
 I have spoken with Dave Jencks and Jeremy about the change and we think this 
 is the best way to proceed.
 I don't know what appliacations may be relying 
 If we agree to make this change this improvement does the following:
 1. Updates all artifacts in the current Geronimo Build to include the TranQL 
 Vendors connectors and remove all references to the Geronimo-Derby-Connector.
 2. Updates OpenEJB to pull the correct version of the TranQL connector
 3. Updates the sandbox PetStore Project to pull in the new connector as well.
 4. Console Update to change the connector class (imbedded as a string in one 
 of the portlets.
 I am finishing the patches to update the various components and testing them 
 out.  Given the magnitude of the change (updating multiple projects) I wanted 
 to get this out for discussion now.  Patches should be ready in a day or so 
 after I've verified them.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira