[
https://issues.apache.org/jira/browse/GERONIMO-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks closed GERONIMO-3904.
----------------------------------
Resolution: Invalid
Assignee: David Jencks
AFAICT this is a request for information rather than a problem.
JDBC has truly bizarre classloading requirements that are pretty inconsistent
with use in an enterprise environment and one consequence of these rules is
that the derby classes must be loaded in only one classloader or they
completely stop working. Since we've loaded them in system-database, any other
derby pool has to get the derby classes from the system-database classloader.
You do this by using system-database as a parent, which is why it is the only
choice when constructing a derby pool.
On the other hand, although the tranql adapter classes are already present in
system-database, an adapter is a javaee application and so deploying it
involves copying the application contents into the deployed module. In this
case the result is that although the tranql connector classes are already in
the parent system-database classloader we copy them into the pool we're
constructing anyway. This takes up more disk space but causes no other harm
AFAIK.
If there is an actual problem please reopen and explain more clearly.
> Creating a new Derby Datasource using the Geronimo Datasource wizard does not
> enlist Derby jars
> -----------------------------------------------------------------------------------------------
>
> Key: GERONIMO-3904
> URL: https://issues.apache.org/jira/browse/GERONIMO-3904
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: databases
> Affects Versions: 2.1
> Environment: Ag 2.1, Windows Xp
> Reporter: Ashish Jain
> Assignee: David Jencks
>
> I am creating a Embedded derby XA datasource using Geronimo Database Pool
> Wizard. While selecting the Driver Jar I could only find
> org.apache.geronimo.configs/system-database/2.1/car listed. However I
> continue creating the datasource and was able to deploy the datasource
> successfully. In plan.xml which is at the following location
> <GERONIMO_HOME>/repository\org\apache\geronimo\configs\system-database\2.1\system-database-2.1.car\META-INF.
> I found
> <dep:dependency>
> <dep:groupId>org.tranql</dep:groupId>
> <dep:artifactId>tranql-connector-derby-embed-xa</dep:artifactId>
> <dep:version>1.3</dep:version>
> <dep:type>rar</dep:type>
> </dep:dependency>
> which suggests that the jar is already included into system-database as a
> dependency.
> 1) Is this the reason for only listing system-database in the available jars.
> 2) Why is that we are using system-database for datasource creation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
