db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@apache.org>
Subject Re: problems building j2me
Date Thu, 21 Jun 2007 18:49:31 GMT
Mike Jarmy wrote:

> OK, I actually have Derby working on J9/JclMax now.  The problem was 
> that J9/JclMax was telling Derby that its java.version was "1.4.2 
> subset", which (although technically true) was confusing Derby into 
> trying to load classes that use java 1.4 packages such as java.nio.  So 
> what I did as a quick-and-dirty way to get it working was comment out 
> the static block in org.apache.derby.iapi.services.info.JVMInfo and 
> replace it with the following code:
>         JDK_ID = J2SE_13;
>         J2ME = false;  // JclMax is a superset of J2ME
>         JAVA_SQL_TYPES_BOOLEAN = java.sql.Types.BIT ;
> Everything seems to work fine now.  It would be nice if there was a more 
> graceful way to handle this though.  If anyone has suggestions for how I 
> ought to modify JVMInfo to properly handle this situation, I'd be glad 
> to contribute the code back to the project.  Although JclMax is not an 
> official Java profile, it is an IBM product, just not a 
> 'coffee-cup-branded' one. 

I think this could be handled by modifying the modules.properties,
that file defines which modules are available and their requirements for 
  running, it's basically Derby's IoC framework.

There are these lines in the file for the raw storage layer:


# Generic version using older IO interfaces

One could modify the first to also indicate that the module requires 
certain classes to run, something like adding one line to the "J4" version:


I haven't tried this and maybe there are other entries that would need 
changes, but it's a starting point for you. It would be great if you 
could contribute a working patch back.


View raw message