RE: Initiating SOAP Request from RPG Using Sockets

Thanks Joe, I understand.  Yes, I agree that Java would be easier in
this case.  We may actually end up doing that.  The project originally
called for an investigation into all viable options other than RPG but
they were asked to spend a few days just seeing if it was viable to use
RPG to initiate the request. 

Just curious, you state that it only creates a JVM on the first call.
Is this assuming that the RPG program will not be shut down after the
call?  I believe that they are going to write a separate RPG program
that would be called from the OMS each time it decides it is necessary
to retrieve the desired info from the service.  In that scenario, would
only one JVM still be invoked?  I guess I'm thinking that each call to
the RPG program would instantiate a new object from the prototyped
class?  If it wouldn't invoke a new JVM in this case, I may be able to
go back to them with this as a viable solution.  

Thanks again for your help.
- Andy

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx
[mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta
Sent: Monday, August 22, 2005 4:01 PM
To: 'Java Programming on and around the iSeries / AS400'
Subject: RE: Initiating SOAP Request from RPG Using Sockets

> From: Andrew Papada
> 
> Thanks for the response (I guess)...I'll try to be more professional
in
> mine:

Walden might have been a bit sarcastic, but I think he was right on
point: use the right tool for the job.


> Yes, I'm very well aware of that there are plenty of easy ways to do
> this in Java, I am J2EE engineer.  I'm writing this on behalf of some
> folks in our OMS group which is comprised of RPG developers and the
> director of that group would like to keep it RPG if possible so not to
> introduce a learning curve in a critical point within the project.

Walden's point is that this is better done in Java.  There are a LOT of
things better done in Java and you're far better off introducing a piece
of Java (tested and working) than trying to rewrite the same thing in
scratch from RPG.


> Additionally, if you invoke the Java class from your transactional RPG
> application by prototyping the method, you're creating a new JVM every
> time you invoke it, thereby decreasing your performance on a system
that
> can ill-afford to be maxed out.

Not true.  You don't create a new JVM, you create one on the first call.
There are other options as well, such as having a server job waiting for
requests.

The point still is that rewriting SOAP in RPG is probably a waste of
resources.

Joe