OpenBaseMovil 3.0.01 released
This is a minor, though important, change.
Nik reported a bug that said that resource-packer would not run on Windows platforms, that in fact was affecting the viewcompiler also.
It is now fixed and tested on Windows XP Pro. We did not remember that there still people (developers) using Windows 
We have not changed the release on sourceforge, it remains 3.0, but we have removed the binary and source files named 3.0 and uploaded new ones with version number 3.0.01:
openbasemovil-3.0.01-bin.zip
openbasemovil-3.0.01-src.zip
We have also added a new binary file called openbasemovil-3.0.01-buildtools.zip that contains only the jar files for the build tools, so to fix the bug in the binary distribution you can download only this one and override the libraries in the 3.0 files.
Sorry for the inconvenience, and thanks for your help.
PS: Try Ubuntu! you wont be disappointed.
Nik
Hi, Narciso.
Thanks for fixing this platform dependent bug.
PS. In Russia most developers using windows os.
PSS. Java programs must be cross-platform.
Narciso Cerezo
Hi Nik,
It was just a joke
We wanted to release soon, and we forgot to check that it actually run on Windows.
In fact, the bug was due to a late change in the ant tasks. We needed to change from ant 1.6 to ant 1.7 and we don’t know why the tasks stopped to work and we had to change the way they took the file names, and thus the bug.
Please keep us informed of your progress or any issues.
Thanks.
Stefan
Hi Narciso,
first of all, thanks for the Framework, it looks very promising
Right now I’m trying to get the DB to work on a Blackberry Device.
But “Database.connect” and “Database.create” always fail.
I copied the Database.connect part from the PasswordKeeper Application to be sure I did it right.
Anyway, here is what I get in the Log when I start my application:
Running with “Database.create”
——————————
Listing RecordStores and trying to delete each one…
sys_error_log
testdb_db
sys_store_info
creating database
Error: exception.ERR_RECORDSTORE[15107] : java.lang.NullPointerException
20080125 151241 Database.saveHeader()
java.lang.NullPointerException: null
20080125 151241 Store.close()
[testdb_db]
java.lang.NullPointerException: null
Running with “Database.connect”
——————————
Listing RecordStores and trying to delete each one…
javax.microedition.rms.RecordStoreException: testdb_db
sys_error_log
testdb_db
sys_store_info
sys_devinfo
connecting to database
Error: java.lang.NullPointerException
20080125 151530 Store.loadRecord(1)
[mapped record id not found (Store: testdb_db, mpx: 1)]
javax.microedition.rms.InvalidRecordIDException: testdb_db #1
20080125 151530 Store.makeCurrent(1,false)
[Invalid record]
exception.ERR_GENERIC[15111] : testdb_db #1
Any idea what’s wrong?
If you need any more information, let me know, I’ll be happy to provide you with what I got.
Thanks in advance,
Stefan
Narciso Cerezo
Hi Stefan,
Thanks for your information, BlackBerry is not now in the supported devices list, but we are very interested in it.
If you could file the comment as a support request we’ll be thankful, we want to keep track of all support request, bugs and feature request through SourceForge.
We run some test some months ago and we are about to do some more in the upcoming weeks.
In those tests the application would run fine, but the RMS system that the BlackBerry exposes is limited in that a RecordStore can not hold more than 64Kb of data, so it was not very functional for our commercial platform since the files usually are bigger in most cases. (we are planning a new version to override that barrier also present on other phones)
I must say that the test were performed with a previous version of our commercial platform. The version is not that important, but it is the way of creating and populating the database.
Our commercial platform uses a synchronization engine that creates, populates and updates both the database structure and data, everything over the air. So the methods for database creation and structure handling are the most new.
We will look at the code with the information provided in order to find where the problem can be, and update you as soon as possible.
By the way, I think that one of the most powerful things in the framework is the ui engine being data aware and soon also script aware, and using XML for the definition.
We have not explained yet that in the tutorial and documentation, but the ui interface can generate both enhanced graphical screens and native LCDUI screens (not as functional, but useful for some purposes), you just need to change the default mode globally or in view-by-view basis. I think the DTD is pretty explanatory.
I say this because you talk about the database engine.
Are you planning to use it and not use the ui library? If so, why?
It’s simple curiosity
regards
Stefan
Hi Narciso,
thanks for your reply
Right now, we don’t plan to use the GUI framework, because we have our own. But right now it lacks a real database component. It would be nice to have one for a project we’re doing right now, but we don’t have the time to do one ourselves. So I was looking all over the Internet to find a good one and up to now, yours was the most promising
Narciso Cerezo
hi Stefan,
Thanks for the info, we are very pleased to hear that kind of comments.
I don’t know if you’ve read about the project history, but the development of the framework has taken about 3 years, and near two of production use.
The j2me database is the 2nd most difficult part, and without doubt the 1st place is for the sync engine (both client and server).
Regards