Comments on: How MIDlet Signing is Killing J2ME

By: Sydwell Williams

Sydwell Williams — Fri, 12 Aug 2011 18:48:41 +0000

J2ME still massively important in the "Developing World" Although cellphones have almost 100% penetration in South Africa We did not have time to run up massive debts to buy iPhones etc.. sorry I could not help my self.

I am curious how J2ME application like MXiT and the like manage to get their programs working on most phones.

But real question is; I purchased code signing certificate from Thawte by I am still struggling to get working on my development phone a Samsung Jet S8003, has anyone managed to run a signed J2ME on this phone?

Kudos to one of the longest running blogs

By: Bob

Bob — Mon, 16 May 2011 20:23:03 +0000

I pasted the wrong link. It should’ve been http://j2start.com/

By: Bob

Bob — Mon, 16 May 2011 20:17:23 +0000

Have any of you tried this: http://javaverified.com

They sign midlets for free

By: andrew

andrew — Thu, 13 Jan 2011 17:30:59 +0000

Another idea would be to create a website with which phones currently are shipping with verisign or thawte or other certificates in them which still allow J2ME apps to run. It could be some sort of wiki linked to a database where users can add in what certificates they have on their phone.

Then at least coders could publish which phones they expect their stuff to run on.

By: andrew

andrew — Thu, 13 Jan 2011 17:21:21 +0000

Excellent blog thanks

Wouldn't it be good if someone wrote some kind of wrapper/firewall type application that was java verified that was unable to commit offences but could run other jad files within itself ... Maybe allowing the user to select which JSRs or functionalities the jad file was allowed to use ... It would be a kind of interpretter running within the JRE interpretter!

I guess getting it passed though would be fun!

By: J2ME restricted APIs – O fim do Java para hobbistas « O desenvolvedor

J2ME restricted APIs – O fim do Java para hobbistas « O desenvolvedor — Sun, 28 Nov 2010 21:38:43 +0000

[…] Link: JavaBlog – How MIDlet signing is killing J2ME […]

By: Guy Berliner

Guy Berliner — Tue, 09 Nov 2010 16:46:07 +0000

So, on a slight side note here: Is the general consensus to avoid Motorola like the plague — even their Android devices? (I’ve read, for example that on some (all?) of their new Android product deliveries, they have conveniently omitted the “unknown sources” option altogether from their software install wizard, tho I gather there are workarounds for rooted phones).

By: Andy Parker

Andy Parker — Sat, 09 Oct 2010 08:11:25 +0000

I’ve ported all our apps to Android, no problems with permissions and certs. So get yourselves an APhone and start using the Android Market Place!

By: Funtikar

Funtikar — Sun, 26 Sep 2010 03:42:14 +0000

Heck I dont think the signing will kill hobby j2me cuz as you’ve mention about the david hayes way or you could just use the Darkman cert which spreading pretty fast now in the wap world. It is possible to also distribute your or Darkman cert along with ur app if it’s for j2me hobby only.. Haha..please excuse me for intruding..

By: eric

eric — Sun, 13 Jun 2010 12:40:30 +0000

hmmm just looking back at this article (I commented on it in 2007).

And Sam, turns out you were completely correct, JME is still there although considering it was the foremost mobile app dev platform at one stage, I think you could now consider it to be dead or at least on its death bed.

That certainly seems to be the case when comparing it to iPhone and Android - both platforms that don't have the anything like the same security / permission mess that JME has and also both platforms that most people had not even heard (didn't even exist?) of when this article was written.

Shame the handset manufacturers / network operators and Sun persisted in their bone headed arrogance. Should've listened to the developers! It's quite sad when you think of what could have been. Oh-well, onward with iPhone and Android for the moment.