posted 22 years ago
This is a hot topic. At JavaOne 2000, I aksed baout this. was told the JAM ws specifically created with this in mind. The concern was that a trojan horse of other malicious program can start modifying a running midlet, or midlet suite.
From a developer's perspective, this is a major handcuff! However, technically, it is not prohibited in the MIDP specification.
Basically, the JAM was a good idea, but not really thought out. I've had discussions with people in both the MIDP and PDAP EG's about being clearer on this in future releases. I suspect they will be.
From talking with vendors, they seem to be creating different types of JAMs. Some will be more flexibile than others, and allow things such as what you describe. What times means in terms of spceification compliance, I have no idea. Ultimately, I think with enough pressure from developers this will be made avilable. Unfortunately, we have to go up against pressure from the very overprotective carriers, so it may be a while.
In the mean time, all I can suggest is keep asking around, and hope you find someone. (You could start by looking at J2ME and device vendors who were at JavaOne last year.)
--Mark
Mark Herschberg, author of The Career Toolkit
https://www.thecareertoolkitbook.com/