db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-646) In-memory backend storage support
Date Mon, 16 Feb 2009 12:37:06 GMT

    [ https://issues.apache.org/jira/browse/DERBY-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673865#action_12673865

Kristian Waagan commented on DERBY-646:

If your classes aren't referenced by any other classes used by Derby,  they won't be included
in the jar file(s).
Assuming you are setting properties to wire in your implementation, you probably need to add
your "root class(es)" to 'tools/jar/extraDBMSclasses.properties'.
As you can see, there are many other classes in there. These are used as roots to determine
which classes to include in the jars.

Hope this helps,

> In-memory backend storage support
> ---------------------------------
>                 Key: DERBY-646
>                 URL: https://issues.apache.org/jira/browse/DERBY-646
>             Project: Derby
>          Issue Type: New Feature
>          Components: Store
>         Environment: All
>            Reporter: Stephen Fitch
>         Attachments: derby-646-1a-raw-compiles.diff, derby-646-1a-raw-compiles.stat,
> To allow creation and modification of databases in-memory without requiring disk access
or space to store the database.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message