You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org> on 2006/11/09 20:13:37 UTC
[jira] Reopened: (GERONIMO-1986) TranQL Connector doesn't check
Driver Class during deployment
[ http://issues.apache.org/jira/browse/GERONIMO-1986?page=all ]
Vamsavardhana Reddy reopened GERONIMO-1986:
-------------------------------------------
Comment from David Jencks on rev 472993 and 472998:
You are assuming that any connector that
has a config-property called "Driver" uses that property for a java
class name that is expected to be on the classpath. I can easily
imagine a jdbc wrapper for a specific database that has a "Driver"
config-property to choose between a type 2 and type 4 driver and e.g.
the property is an Integer rather than a class name.
I think we could either
-- emit a warning if the class can't be loaded rather than throwing
an exception
or
-- only do this check if we are loading the tranql generic jdbc
wrapper in some version.
> TranQL Connector doesn't check Driver Class during deployment
> -------------------------------------------------------------
>
> Key: GERONIMO-1986
> URL: http://issues.apache.org/jira/browse/GERONIMO-1986
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: connector, deployment
> Affects Versions: 1.1, 1.1.1, 1.1.2
> Reporter: Aaron Mulder
> Assigned To: Vamsavardhana Reddy
> Fix For: 1.2, 1.1.2
>
> Attachments: db-plan-no-deps.xml, tranql-1986-updated.patch, tranql-1986.patch
>
>
> If you deploy the attached plan with the TranQL connector RAR, the distribute phase is successful, but it fails during start because the driver class is not available.
> It would be much better to find a way to validate the driver class during distribution. I'm not sure how complex this will be; it may involve instanting things during distribution that normally aren't instantiated until start time. But the current behavior is definitely not desirable.
--
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