This content has been marked as final. Show 4 replies
I can't find something relevant to what I want which is launching another midlet.Can't be done in MIDP 2. There was some talk about this ability being added in MIDP 3, but I don't know what the progress on that is.
I may have missed something.Nope.
How about this link http://www.java-tips.org/java-me-tips/midp/launching-a-midlet-from-another-midlet.html ?
Has anyone tried before? It seems like it may work but i just cant seem to find the way to package a given jar file (with 1 midlet in it) with another midlet which can call the original midlet.
That's a different matter. The second MIDlet is launched by the Application Manager at the scheduled time, not by the MIDlet that books the PushRegistry alarm. And there's no way you can possibly
go back to my midlet again.Apart from which, many devices will ask the user's permission before launching an application scheduled by PushRegistry, so even the first part of your requirement can't be guaranteed to be seamless.
Why do you think you need this? There may be an easier solution, like using related classes with only one MIDlet.
812631 wrote:You could unpack the jar and pack the needed classes, along with your own, in a new jar. If the license permits you to do that. And if we're talking about commercial software, it almost certainly doesn't.
i just cant seem to find the way to package a given jar file (with 1 midlet in it) with another midlet which can call the original midlet.