Push Registry Problem

[Emproy]

Hi all:

I have a proyect in J2ME with 2 midlets. I start one of midlets with push registry from the other midlet with socket connection.
In the JAD file, I insert the 2 midlets that appears in the screen. But this registy in the JAD file causes that user's terminal can show 2 midlet to access to the application, and I want that the users only can see one midlet.

How can I do that the second midlet can't be active by user directly or how can I active a midlet with other midlet?

This is my JAD file:
MIDlet-2: PruebaPush1B,,PruebaPush1B
MIDlet-1: RegistroConexionB,,RegistroConexionB
MIDlet-Jar-URL: PushSocketBueno.jar
MicroEdition-Configuration: CLDC-1.1
MIDlet-Push-1: socket://:1712,PruebaPush1B,*
MIDlet-Version: 1.0.0
MIDlet-Name: PushSocketBueno Midlet Suite
MIDlet-Vendor: Midlet Suite Vendor
MicroEdition-Profile: MIDP-2.0
MIDlet-Permissions: javax.microedition.io.PushRegistry,javax.microedition.io.Connector,javax.microedition.io.SocketConnection

I want that the users can access to the MIDlet-2.

Thanks all.
Em.

[grahamhughes]

You cannot hide a MIDlet within a suite. Well... you could try omiting the MIDlet-n attribute from the JAD and MANIFEST, but you might find the push-registry won't like a MIDlet class that isn't declared in the descriptor.

The thing to do would be... just have one MIDlet. Don't split the application into two parts. Why do you want to have two MIDlets? It just seems to be adding a complication.

Graham.

[Emproy]

Hi Graham:

Thanks for your help.
If I omite the MIDlet-n attribute in the MANIFEST, my proyect can't be installed in the emulator (I'm working with Emulator S60 Nokia N97).

If I divide my proyect in two proyects,with one midlet each one; How can I do that one of proyects be invisible for the user?? This proyect must work in background.

Thanks for all.
Em.

[grahamhughes]

You cannot have an invisible MIDlet.

Why not just create one MIDlet with all the functionality? Why do you want two MIDlets?

Graham.

[Emproy]

My proyect has 2 parts.
One part contains an user interface, and the other part is a module (a search system) which receives information from the user interface and from other module (an intelligent agent- I am not going to implement it).
I need that this module "wake up" when receives an information from anywhere ( the user interface or intelligent agent) and the user can't access to this search system directly.

Because of it, I thought that the push registry could be an option.
Could I implement the search system without midlet? (other alternatives?)

Thanks.
Em.

[grahamhughes]

What would be the nature of the "intelligent agent"?

[Emproy]

I don't implement the intelligent agent but this will be in the same terminal.
I only know that I must provide it the access to the search system.

[grahamhughes]

You will certainly need to implement the UI and search system in the same JAR, with only a single MIDlet.

I can't suggest how the "intelligent agent" might attach to the search system, without knowing what it is.

Graham.

[Emproy]

Hi Graham:

I don't need know how connect the intelligent agent, it is only important for know that I must separate the proyect in 2 parts.
The push registry is one possible solution, but it use midlets and I want know how do for the user can't access to the second part.
I have learn something about digital signature.
Do you know anything about this?
Could I use this with push regitry?

Thanks for all, Graham.
Em.

[grahamhughes]

I don't need know how connect the intelligent agent, it is only important for know that I must separate the proyect in 2 parts.

It is hard to suggest how to separate the search engine without knowing all the different scenarios in which it might be used.

I can only recommend that you use object orientation to separate the search engine as a component with a clearly defined API, and treat it like a library.

Is this an accademic or commercial project? On what devices must it work?

The push registry is one possible solution, but it use midlets and I want know how do for the user can't access to the second part.

There is no way to prevent access to a MIDlet.

I have learn something about digital signature.
Do you know anything about this?

For information about signing, start here.

Could I use this with push regitry?

Signing will not help you hide one of your MIDlets.

Graham.

[Emproy]

This is my device:

(I'm working with Emulator S60 Nokia N97).

My project is accademic, but is it really important?

I don't want prevent access to a MIDlet.
I want the user can't access to the project from the midlet which must "wake up" with push registry, because, the push registry forces to register this midlet in the JAD file, and this causes that in "Applications" in main of emulator N97 shows this midlet.

I want the user only can access to the project from the midlet which "wake up" to the other midlet.Is it not possible too?

Thanks.

[grahamhughes]

I want the user can't access to the project from the midlet which must "wake up" with push registry, because, the push registry forces to register this midlet in the JAD file, and this causes that in "Applications" in main of emulator N97 shows this midlet.

I want the user only can access to the project from the midlet which "wake up" to the other midlet.Is it not possible too?

You cannot hide a MIDlet within a suite.

You cannot have an invisible MIDlet.

There is no way to prevent access to a MIDlet.

I don't know how else I can answer your question.

I suggest you forget the idea of using the push-registry. You're trying to create a client-server model, with a MIDlet as the server, and MIDlets are not well suited to this.

Graham.

[Enthusiastic]

Hii,

could u please tell us more abt ur project. What all features it has.
Then we can discuss how u can implement that... either by PushRegistry or some other way.


Nikesh~
Enthusiastic

[Emproy]

Thanks Graham.
My project is accademic and I can't change this yet.
I will search some alternative.

Forgive the inconvence and thanks for your help, Graham.


Hi Enthusiastic, I think that the important features are in this thread.
Thanks for your interest.
If you know some altenative, Could you say me, please?
Thanks.

Em.

[Enthusiastic]

Hii,

okk emproy. Which PushRegistry u r planning to implement is it SMS based.
if it's SMS based then u can do this by this way also...
as grahamhughes said u can't hide/make invisible/prevent access to MIDlet. Let user open the another midlet. When the MIDlet will start u'll come to know this is a ato invocation or ser has started it his own by...

connections = PushRegistry.listConnections(true);