db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (DERBY-3703) Make it possible to build the JSR169 support with the jdk1.4 libraries
Date Tue, 03 Jun 2008 03:38:45 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601819#action_12601819
] 

djd edited comment on DERBY-3703 at 6/2/08 8:37 PM:
----------------------------------------------------------------------

-1 on this patch unless this question can be answered:

   How do you guarantee that classes (java.sql.Ref, Struct etc.)  that are not in JSR 169
or CDC/Foundation but now are referenced in the classes used to implement Derby's JDBC driver
for JSR 169 will not cause ClassNotFoundExceptions or LinkageExceptions in all J2ME/CDC/Foundation
implementations?

[edit]
Note the current implementation makes that guarantee by not referencing undefined classes
in the classes used to implement Derby's JDBC driver for JSR 169.

      was (Author: djd):
    -1 on this patch unless this question can be answered:

   How do you guarantee that classes (java.sql.Ref, Struct etc.)  that are not in JSR 169
or CDC/Foundation but now are referenced in the classes used to implement Derby's JDBC driver
for JSR 169 will not cause ClassNotFoundExceptions or LinkageExceptions in all J2ME/CDC/Foundation
implementations?
  
> Make it possible to build the JSR169 support with the jdk1.4 libraries
> ----------------------------------------------------------------------
>
>                 Key: DERBY-3703
>                 URL: https://issues.apache.org/jira/browse/DERBY-3703
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>            Reporter: Rick Hillegas
>         Attachments: derby-3703-01-aa-moveJdbc3methods.diff, derby-3703-01-aa-moveJdbc3methods.diff
>
>
> It would be good to simplify the Derby build so that the whole product could be built
out-of-the-box just from what's checked into the Derby repository. As a step toward this goal,
it would be good to be able to build the jsr169 support without having to download proprietary
libraries.

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


Mime
View raw message