A
Araxes Tharsis
Hi,
I am creating an application with Java SE that needs to expose
functionalities of a mainframe to .NET clients. I am thinking in creating a
Web Service with methods:
void startEngine()
void shutdownEngine()
String[] doCommand( String[] )
As I must have only one engine running, I will make the scope of the WS as
"Application". The first client must start the engine with startEngine() and
then all clients can use the same engine that is running with the
doCommand() method. Is this correct?
As I need to monitor the operations of the engine I will make it a RMI
Server, so I can access it with an Applet, that will have to be made
available by the startEngine() method. As I want to be able to start the
engine from the Applet I will also need to use the WS mentioned, from the
Applet.
Anything wrong with this Architecture?
Any comments appreciated.
Thanks,
Araxes Tharsis
I am creating an application with Java SE that needs to expose
functionalities of a mainframe to .NET clients. I am thinking in creating a
Web Service with methods:
void startEngine()
void shutdownEngine()
String[] doCommand( String[] )
As I must have only one engine running, I will make the scope of the WS as
"Application". The first client must start the engine with startEngine() and
then all clients can use the same engine that is running with the
doCommand() method. Is this correct?
As I need to monitor the operations of the engine I will make it a RMI
Server, so I can access it with an Applet, that will have to be made
available by the startEngine() method. As I want to be able to start the
engine from the Applet I will also need to use the WS mentioned, from the
Applet.
Anything wrong with this Architecture?
Any comments appreciated.
Thanks,
Araxes Tharsis