Well, there's a pretty good chance that it is something in my local settings. Running on a server edition of Windows is guaranteed to take you through all kinds of interesting option dialogs before you get you 3d apps working with any kind of frame rate. :-)

I've had some good experience with me4se, which is a library that emulates the J2ME API on a standard JRE/JDK. You can find out more about it at www.me4se.org.

Rob, I actually meant that the performance was not pretty. The rendering result itself looks ok.

Yesterday I did some further investigation as to why performance would be this bad and found out that on Windows 2003 Server it uses software rendering by default. That probably explain the crappy performance I've been getting.

I switched video rendering to using full hardware acceleration and most apps now perform much better.

With your kit2 app however, I only see the initial frame being rendered. After that the image remains static, even though the status bar keeps getting updated. The figures in the status bar now actually show more reasonable performance (26fps). But it would be nice if I could actually see some of those frames being rendered. :-/

Just ran it at the office to see what it does here. The results are not pretty:
Win2003, P4 2.4GHz, Intel Extreme driver version 6.13.1.3259, 3.1fps

Serethos: Jeode is pretty close to a J2SE SDK. So you do you development on a standard PC, keeping in mind of course that you'll deploy to device with a much lower resolution.  

One of the cool things I've done (not created) is running J2ME midlets on my PocketPC. This is made possible by using Jeode as a JVM and then running me4se on top of it. The latter is an emulation layer for running J2ME code on top of a J2SE runtime. This also allows you to develop J2ME midlets on a standard J2SE development kit.

I agree that there should be something like that. But unfortunately there isn't. Sun seems to have dropped all support for PocketPCs since it shipped a Personal Java release for Windows CE 2.x.

Fortunately there is some hope. SuperWaba seems to work fine on PocketPCs and I've actually seen some recent game releases that were made with it. Another alternative is the Jeode VM, which is a commercial VM. I find it a bit expensive but have heard people had good experiences with it.

You're right, it is HIGHLY dependant on the exact implementation.  I probably shouldn't have made a claim that far fetched. Sorry about that.

But I happen to like the syntactic sugar that the forEach is offering, so I'm looking for workarounds for the problems. Since I've had similar problems with standard Iterators, I was looking for a solution that works in all cases. Having a second collection of objects should always work, although not at the best possible speed.

Given the available development time saved versus the deployment time lost, it might be worth using in some cases.

I was just thinking about this a few days ago. The easiest way to solve the problem is to add the objects to a secondary collection during the forEach and then remove them all in one go after the loop.

So it should be something like this:

Collection<SomeObject> removableObjects = new Collection<SomeObject>();
for (SomeObject o: someCollection)
{
 if (!o.someCondition())
   removableObjects.add(o);
}
someCollection.removeAll(removableObjects);

It actually allows the JVM to more efficiently remove the objects all in one go, although I doubt whether it will make much difference at the moment.

            Puf

I'm not sure what you're trying to accomplish, but if you just want to have midlets running on your standard Java distribution on the mac it should be relatively easy using ME4SE.

As the name suggests this allows you to run J2ME programs on any J2SE distribution. It consists of one major jar and a few helper jars. It can be gotten from www.me4se.org.

I've used it on both my Windows machine as well as a PDA, so a Mac should work fine too given that their JRE implementation is not too bad.

You're probably talking about the JGears demo right? I had the same problem with a GeForce on my laptop. It seems to have something to do with the software rendering of that specific demo. I have no idea what caused it, but have not had any such problems with other demos or my own code. My advice: don't worry about it and just look at other demos.

The first question you need to ask yourself is if you really want the database to reside on the j2me device.

Keep in mind that relational databases tend to grow large pretty fast. And since most j2me devices have not much memory, it might not be an option. Of course this really depends on you intended target device(s) and usage scenario.

If you really need the database on the device, also keep in mind that you need to have a library that allows you to access the MDB (access database) on the device. On a j2se or j2ee system you would use JDBC for this, but that's probably not an option for a j2me device due to the size of such libraries.

Does this help? If so, then please answer the question whether you really need the database to be physically on the j2me device.

I've succesfully run midlets on my pocketpc using jeode combined with me4se. The latter is basically a jar that allows you to run j2me programs on a j2se runtime. It can be found at me4se.org.