The MIDP spec talked very little about OTA (over the air) provisioning. It basically waved its hand on the subject and avoided it. It's mostly vendor specific. I created a (patent-pending) custom solution at my last company. JSR-124 may also have some bearing on this area. Although it is J2EE, MIDlets and similar application may be supported by J2EE backends. Note that phone companies have a very different (read: protective) culture, wrt their devices, and so will be slower to adopt such systems. --Mark
It is current no, and not likely anytime soon. However, these concepts make even more sense on wireless devices then on desktops. I suspect we'll see some basic functionality soon, OTA stuff, but expanded functionality not for a while. We'll also see it first on handhelds, before phones, simply because, as I said before, the phone companies aren't very open with their hardware. --Mark
Hi Burk, If you're interested, in the book (that doesn't cover ONLY JNLP, but the whole Java deployment issue as a whole) I consider J2ME MIDP advanced deployment services, with some working example code. As for JNLP in the Java wireless world I am a bit skeptical, because of the bandwidth costs associated with XML files and the overall JNLP mechanism. Maybe on more complex profiles in the future, but as it is now, the JNLP protocol seems a bit too desktop-centric. Cheers, Mauro
As for JNLP in the Java wireless world I am a bit skeptical, because of the bandwidth costs associated with XML files and the overall JNLP mechanism.
In my wireless product, we got up to 70-80% compression on our XML data. I haven't looked at the JNLP wireline protocol that closely. I wonder if there's a way to embed or call out to a compressional alogithm to cut down on this overhead. I'm sure it could be done, because I can't imagine the specs would be so detailed about an implementation. --Mark
Mark, I wasn't clear in the previous post, sorry. It's not a mere bandwidth problem. JNLP was designed specifically for the Java 2 Standard Edition, in that uses custom classloaders to implement some of its features "gracefully". Having said that, maybe they will change the specs in the next future, but as it is now is strongly targeted _only_ to the J2SE.
Okay, for now Web Start is J2Se based. I didn't know it was using class loaders though. I got to attend a session on creatign and using custom class loaders at JavaOne. Seems like a pretty cool thing. I guess I need to spend some of my copious free time looking into them too.
SCJP, SCJD, SCEA 5 "Any sufficiently analyzed magic is indistinguishable from science!" Agatha Heterodyne (Girl Genius)