Hi Thomas,
I'm a little bit confused about your questions, so I'll ask some questions and hopefully you can help me understand what you are trying to do.
Let me state what I know about the Derby plug-in right now to help clarify:
1) From an application developers point of view the Derby jar files can be added to individual projects in a workspace either "manually" using just the Derby core plug-in, or automatically using the Derby UI plug-in via a menu item.
2) From an application developers point of view a Derby database that is created via the url "jdbc:derby:myDB;create=true" is added to the project in the workspace where the derby jar files where added.
3) A derby database can be created using a full file system path. In other words, the database does not have to be created relative to a directory - a full system path can be specified.
Now, regarding your comments and questions:
When you say "the embedded system is configured to use one single root where all databases are stored" - are you referring to your plug-in as the "embedded system"? I'm not sure what you mean as the embedded system.
Can you elaborate what you mean by this statement:
"If my plugin defines this property to some location (say the state location for the plugin), it will make it impossible to other plugins that also wish to use Derby in the same Eclipse instance."
When you say impossible to other plugins that wish to use Derby in the same Eclipse instance do you mean the same Derby database? Is this Derby database used to store metadata for the plug-in or is it an application database?
So are you saying that all plug-ins that use the Derby plug-in for metadata for their plug-ins should store databases in the Derby plug-in state directory?
Also, you mentioned this "root" is on a per JVM basis. As you probably know if you are using an embedded Derby database, only one JVM can access this database at one time. I'm not sure if this is relevant to what you are talking about or not.
Regarding the need for a more elaborate Derby plug-in is your desire for the Derby plug-in to specify the derby.system.home to be the state directory of the Derby plug-in, for all derby databases created from within the Eclipse JVM?
If so, this capability does not exist with the current plug-ins.
Please let me know how I can help by letting me know if I have understood your question.
Regards,
Susan
Note: forwarded message attached.
I'm a little bit confused about your questions, so I'll ask some questions and hopefully you can help me understand what you are trying to do.
Let me state what I know about the Derby plug-in right now to help clarify:
1) From an application developers point of view the Derby jar files can be added to individual projects in a workspace either "manually" using just the Derby core plug-in, or automatically using the Derby UI plug-in via a menu item.
2) From an application developers point of view a Derby database that is created via the url "jdbc:derby:myDB;create=true" is added to the project in the workspace where the derby jar files where added.
3) A derby database can be created using a full file system path. In other words, the database does not have to be created relative to a directory - a full system path can be specified.
Now, regarding your comments and questions:
When you say "the embedded system is configured to use one single root where all databases are stored" - are you referring to your plug-in as the "embedded system"? I'm not sure what you mean as the embedded system.
Can you elaborate what you mean by this statement:
"If my plugin defines this property to some location (say the state location for the plugin), it will make it impossible to other plugins that also wish to use Derby in the same Eclipse instance."
When you say impossible to other plugins that wish to use Derby in the same Eclipse instance do you mean the same Derby database? Is this Derby database used to store metadata for the plug-in or is it an application database?
So are you saying that all plug-ins that use the Derby plug-in for metadata for their plug-ins should store databases in the Derby plug-in state directory?
Also, you mentioned this "root" is on a per JVM basis. As you probably know if you are using an embedded Derby database, only one JVM can access this database at one time. I'm not sure if this is relevant to what you are talking about or not.
Regarding the need for a more elaborate Derby plug-in is your desire for the Derby plug-in to specify the derby.system.home to be the state directory of the Derby plug-in, for all derby databases created from within the Eclipse JVM?
If so, this capability does not exist with the current plug-ins.
Please let me know how I can help by letting me know if I have understood your question.
Regards,
Susan
Note: forwarded message attached.
--- Begin Message ---Hi,I'm considering using the Apache Derby as an embedded database for one of my Eclipse plugins. So I downloaded the plugin that Apache makes available. It contains the needed jars etc. but I have one problem.The embedded system is configured to use one single root where all databases are stored. This root is on a per JVM basis (configured using a system property). If my plugin defines this property to some location (say the state location for the plugin), it will make it impossible to other plugins that also wish to use Derby in the same Eclipse instance.The way I see it, a more elaborated Derby plugin is needed that actually defines the single root for all databases for the Eclipse installation where it is used. With that in place, multiple other plugins could express a dependency to it, and thus have coexisting databases without conflicts.My question is, has anyone created such a plugin already? If so, where can I find it? Kind regards, Thomas Hallgren
--- End Message ---
