You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <de...@db.apache.org> on 2005/08/25 19:26:08 UTC
[jira] Created: (DERBY-540) Loading databases from jars in the classpath is broken, databases cannot be found.
Loading databases from jars in the classpath is broken, databases cannot be found.
----------------------------------------------------------------------------------
Key: DERBY-540
URL: http://issues.apache.org/jira/browse/DERBY-540
Project: Derby
Type: Bug
Components: Store
Versions: 10.1.1.0
Reporter: Daniel John Debrunner
In converting an old Cloudscape test to ensure changes made for DERBY-538 would not break loading from classes stored in the database when the database itself is in a jar, I discovered that a database cannot be found that is in a jar on the classpath.
Discovered the reason is the StoreFactory implementation for classpath always prepends a leading foward slash to the database name, but this is incorrect (e.g. db7 to /db7). This causes the database not to be found when the classloader is URLClassLoader as the correct path for the service.properties file is db7/services.properties, not /db7/services.properties.
Will add converted test (lang/dbjar.sql)
--
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: (DERBY-540) Loading databases from jars in the classpath is broken, databases cannot be found.
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-540?page=all ]
Deepa Remesh updated DERBY-540:
-------------------------------
Fix Version: 10.1.1.1
> Loading databases from jars in the classpath is broken, databases cannot be found.
> ----------------------------------------------------------------------------------
>
> Key: DERBY-540
> URL: http://issues.apache.org/jira/browse/DERBY-540
> Project: Derby
> Type: Bug
> Components: Store
> Versions: 10.1.1.0
> Reporter: Daniel John Debrunner
> Assignee: Daniel John Debrunner
> Fix For: 10.2.0.0, 10.1.2.0, 10.1.1.1
>
> In converting an old Cloudscape test to ensure changes made for DERBY-538 would not break loading from classes stored in the database when the database itself is in a jar, I discovered that a database cannot be found that is in a jar on the classpath.
> Discovered the reason is the StoreFactory implementation for classpath always prepends a leading foward slash to the database name, but this is incorrect (e.g. db7 to /db7). This causes the database not to be found when the classloader is URLClassLoader as the correct path for the service.properties file is db7/services.properties, not /db7/services.properties.
> Will add converted test (lang/dbjar.sql)
--
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: (DERBY-540) Loading databases from jars in the classpath is broken, databases cannot be found.
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-540?page=all ]
Daniel John Debrunner updated DERBY-540:
----------------------------------------
Fix Version: 10.1.2.0
Merged 240111 into trunk as revision 290301
> Loading databases from jars in the classpath is broken, databases cannot be found.
> ----------------------------------------------------------------------------------
>
> Key: DERBY-540
> URL: http://issues.apache.org/jira/browse/DERBY-540
> Project: Derby
> Type: Bug
> Components: Store
> Versions: 10.1.1.0
> Reporter: Daniel John Debrunner
> Assignee: Daniel John Debrunner
> Fix For: 10.2.0.0, 10.1.2.0
>
> In converting an old Cloudscape test to ensure changes made for DERBY-538 would not break loading from classes stored in the database when the database itself is in a jar, I discovered that a database cannot be found that is in a jar on the classpath.
> Discovered the reason is the StoreFactory implementation for classpath always prepends a leading foward slash to the database name, but this is incorrect (e.g. db7 to /db7). This causes the database not to be found when the classloader is URLClassLoader as the correct path for the service.properties file is db7/services.properties, not /db7/services.properties.
> Will add converted test (lang/dbjar.sql)
--
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] Closed: (DERBY-540) Loading databases from jars in the
classpath is broken, databases cannot be found.
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-540?page=all ]
Daniel John Debrunner closed DERBY-540:
---------------------------------------
> Loading databases from jars in the classpath is broken, databases cannot be found.
> ----------------------------------------------------------------------------------
>
> Key: DERBY-540
> URL: http://issues.apache.org/jira/browse/DERBY-540
> Project: Derby
> Type: Bug
> Components: Store
> Versions: 10.1.1.0
> Reporter: Daniel John Debrunner
> Assignee: Daniel John Debrunner
> Fix For: 10.2.0.0, 10.1.2.0, 10.1.1.1
>
> In converting an old Cloudscape test to ensure changes made for DERBY-538 would not break loading from classes stored in the database when the database itself is in a jar, I discovered that a database cannot be found that is in a jar on the classpath.
> Discovered the reason is the StoreFactory implementation for classpath always prepends a leading foward slash to the database name, but this is incorrect (e.g. db7 to /db7). This causes the database not to be found when the classloader is URLClassLoader as the correct path for the service.properties file is db7/services.properties, not /db7/services.properties.
> Will add converted test (lang/dbjar.sql)
--
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: (DERBY-540) Loading databases from jars in the classpath is broken, databases cannot be found.
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-540?page=all ]
Daniel John Debrunner updated DERBY-540:
----------------------------------------
Fix Version: 10.2.0.0
Committed revision.
U java\engine\org\apache\derby\impl\io\CPStorageFactory.java
U java\engine\org\apache\derby\impl\io\CPFile.java
A java\testing\org\apache\derbyTesting\functionTests\tests\lang\dbjar_app.properties
A java\testing\org\apache\derbyTesting\functionTests\tests\lang\dbjar.jar
A java\testing\org\apache\derbyTesting\functionTests\tests\lang\dbjar.sql
A java\testing\org\apache\derbyTesting\functionTests\tests\lang\dbjarUtil.java
U java\testing\org\apache\derbyTesting\functionTests\tests\lang\copyfiles.ant
A java\testing\org\apache\derbyTesting\functionTests\master\dbjar.out
U java\testing\org\apache\derbyTesting\functionTests\suites\derbylang.runall
Updated to revision 240111.
> Loading databases from jars in the classpath is broken, databases cannot be found.
> ----------------------------------------------------------------------------------
>
> Key: DERBY-540
> URL: http://issues.apache.org/jira/browse/DERBY-540
> Project: Derby
> Type: Bug
> Components: Store
> Versions: 10.1.1.0
> Reporter: Daniel John Debrunner
> Assignee: Daniel John Debrunner
> Fix For: 10.2.0.0
>
> In converting an old Cloudscape test to ensure changes made for DERBY-538 would not break loading from classes stored in the database when the database itself is in a jar, I discovered that a database cannot be found that is in a jar on the classpath.
> Discovered the reason is the StoreFactory implementation for classpath always prepends a leading foward slash to the database name, but this is incorrect (e.g. db7 to /db7). This causes the database not to be found when the classloader is URLClassLoader as the correct path for the service.properties file is db7/services.properties, not /db7/services.properties.
> Will add converted test (lang/dbjar.sql)
--
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] Resolved: (DERBY-540) Loading databases from jars in the classpath is broken, databases cannot be found.
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-540?page=all ]
Daniel John Debrunner resolved DERBY-540:
-----------------------------------------
Resolution: Fixed
> Loading databases from jars in the classpath is broken, databases cannot be found.
> ----------------------------------------------------------------------------------
>
> Key: DERBY-540
> URL: http://issues.apache.org/jira/browse/DERBY-540
> Project: Derby
> Type: Bug
> Components: Store
> Versions: 10.1.1.0
> Reporter: Daniel John Debrunner
> Assignee: Daniel John Debrunner
> Fix For: 10.2.0.0
>
> In converting an old Cloudscape test to ensure changes made for DERBY-538 would not break loading from classes stored in the database when the database itself is in a jar, I discovered that a database cannot be found that is in a jar on the classpath.
> Discovered the reason is the StoreFactory implementation for classpath always prepends a leading foward slash to the database name, but this is incorrect (e.g. db7 to /db7). This causes the database not to be found when the classloader is URLClassLoader as the correct path for the service.properties file is db7/services.properties, not /db7/services.properties.
> Will add converted test (lang/dbjar.sql)
--
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] Assigned: (DERBY-540) Loading databases from jars in the classpath is broken, databases cannot be found.
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-540?page=all ]
Daniel John Debrunner reassigned DERBY-540:
-------------------------------------------
Assign To: Daniel John Debrunner
> Loading databases from jars in the classpath is broken, databases cannot be found.
> ----------------------------------------------------------------------------------
>
> Key: DERBY-540
> URL: http://issues.apache.org/jira/browse/DERBY-540
> Project: Derby
> Type: Bug
> Components: Store
> Versions: 10.1.1.0
> Reporter: Daniel John Debrunner
> Assignee: Daniel John Debrunner
>
> In converting an old Cloudscape test to ensure changes made for DERBY-538 would not break loading from classes stored in the database when the database itself is in a jar, I discovered that a database cannot be found that is in a jar on the classpath.
> Discovered the reason is the StoreFactory implementation for classpath always prepends a leading foward slash to the database name, but this is incorrect (e.g. db7 to /db7). This causes the database not to be found when the classloader is URLClassLoader as the correct path for the service.properties file is db7/services.properties, not /db7/services.properties.
> Will add converted test (lang/dbjar.sql)
--
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