Sorry for the ignorance, but I'm a but confused about this jar selection...
Does it allows me to have more than one driver version for the same vendor
(like having a Oracle 8i and Oracle 10g drivers at same time being used by
different datasources)? If not, what is the point in selecting the JAR
On Apr 19, 2007, at 2:08 AM, Daniel Alheiros wrote:
Sorry for the ignorance, but I'm a but confused about this jar
selection...
Does it allows me to have more than one driver version for the same
vendor
(like having a Oracle 8i and Oracle 10g drivers at same time being
used by
different
Interesting...
So if my application depends on an OracleDriver or other vendor specific
implementations how my application will be instructed to refer to the
specific implementation (jar) as my class import one of those. How can it
resolve the reference to the correct jar?
An example class:
I don't seem to be explaining what I have in mind very well. I was
thinking of a text entry box on the db wizard page where you;d type
in a fully qualified class name and a button you'd then push, at
which point only jars containing that class would appear in the list
of jars. You could
[
https://issues.apache.org/jira/browse/GERONIMO-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489781
]
David Jencks commented on GERONIMO-3106:
What we have now is surely annoying and hard to use, but there
Well anyway, if you are going to filter by the class, you still have the
problem of not seeing all its dependent classes/jars... But I really think
it shouldn't be a big deal in this context.
Talking about the performance hit related to this kind of filtering, it can
be avoided if you keep track
Just remember that one of the main reasons that there's an awkward
display of tons of JARs now is that the DB2 driver (did? does?)
require 3 JARs to all be added in order to function, and only one of
those has any kind of driver implementation AFAIK. (I think one is a
license and not sure about
