db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernd Lachner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-631) Derby Eclipse plug-in shouldn't use Jar packages in the plugin for better usage in RCP Applications
Date Wed, 19 Oct 2005 08:13:45 GMT
    [ http://issues.apache.org/jira/browse/DERBY-631?page=comments#action_12332459 ] 

Bernd Lachner commented on DERBY-631:

> I'm a little confused by this report. I haven't built an RCP application, so maybe I
am missing something. You mentioned the jar file 
> called org.apache.derby.core_10.1.1.0.jar, is this something that is created when you
build the RCP application? 

Yes this jar file is created when I deploy my application. This jar file than contains derby.jar,
derbyclient.jar, derbynet.jar, derbytools.jar and a plugin.xml. And this don't work because
the Eclipse RCP application don't found the derby classes in this case.

> What happens if you:
> Unzip the derby core plug-in zip file and leave checked the 'Unpack the plug-in archive
after the installation' (however it sounds like 
> this  might cause you a problem, can you explain why?) 

This works without problems. The RCP apllication than contains a directory org.apache.derby.core_10.1.1.0
instead org.apache.derby.core_10.1.1.0.jar with the derby jar files.

> I believe when building an RCP application you can include an entire directory instead
of a jar file when referring to a plug-in? If so, 
> would  this work for you? 

Yes, as I wrote above, this works. The RCP application than includes the same derby plug-in
directory as Eclipse itself.

> You mentioned Java Web Start requires the Derby core plug-in be packed. Does this means
it needs a zip file or a jar file? What is 
> contained in this file?

I'm really new to Java Web Start, especially for Eclipse RCP applications. As far a I know,
for Web Start all Java classes must be packed in jar files. I don't know at the moment if
all plug-ins of the RCP application must be packed in jar files too. Maybe I can get Web Start
work with the directory org.apache.derby.core_10.1.1.0 for the derby plug-in too. I will try

> If so, is the solution to your problem to create a plug-in that only contains all of
the classes of derby.jar in a jar file with a plugin.xml?
Yes this would be the solution. In this case the Derby plug-in can be packed as jar file.

> Please let me know if I have missed the point. Also, for plug-in providers that package
their plug-ins as jar files do these jar files only 
> contain *.class files and the plugin.xml, or do they package it another way?
As far as I know they only contain *.class files, plugin.xml and maybe some other resource
files. In Eclipse 3.1, many, but not all, plug-ins are provided this way. Including all base
plug-ins necessary for a RCP application. You can look in the Eclipse plug-in directory and
in the jar packaged plug-ins to see that.

> Your last comment has me confused as well: 'Maybe in future versions of the Derby Core
plug-in Jars in Jars can be avoided...' , since
> we do not package the plug-ins this way, unless you are referring to a zip file being
the same thing as a jar file.
Yes you are right, this is a little confusing, because you don't provide the jar file with
the derby jar files in it. This jar file is created by Eclipse on deployment time if I uncheck
the 'Unpack the plug-in archive after the installation' option for the plug-in. So the solution
would be, as already mentioned above, to provide the Derby plug-in not as an directory with
jar files and plugin.xml but as a jar file with class files and plugin.xml in it. I think
this would be an improvement for the Derby plug-in.

> Derby Eclipse plug-in shouldn't use Jar packages in the plugin for better usage in RCP
> ---------------------------------------------------------------------------------------------------
>          Key: DERBY-631
>          URL: http://issues.apache.org/jira/browse/DERBY-631
>      Project: Derby
>         Type: Improvement
>     Versions:
>  Environment: Eclipse RCP
>     Reporter: Bernd Lachner
>     Priority: Minor

> I use the Derby Eclipse Core plug-in in an Eclipse RCP Application. If I disable "Unpack
the plug-in archive after the installation" in the feature of my RCP Application for the Derby
core plug-in, the Derby classes can't be found by "Class.forName("org.apache.derby.jdbc.EmbeddedDriver");"
after I deployed the Application and try to start it. It only works when the Derby Core plug-in
is unpacked. It seams, the reason for this behaviour is, that the org.apache.derby.core_10.1.1.0.jar
contains other jar files (derby.jar, derbyclient.jar, ...) and Eclipse RCP can't handle this.
But for example for Java Web Start it would be necessary that the Derby Core plug-in is also
packed. Maybe in future versions of the Derby Core plug-in Jars in Jars can be avoided to
solve this problem.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message