|
Like Barbara said, STATIC.
There's nothing wrong with using STATIC procedures (now that I know the
syntax :-) ). You don't have to go through the pain of running the
CONSTRUCTOR first. If you don't need instance objects, don't use them.
Referencing a static method automatically creates the class object the
first time you use it, but no instance objects. The class object contains
only the static members and methods. But don't call it "main". A class
does not have to have a "main" unless you want the RUNJVA command to start
there. Java function main is really meant for just that; the place to
start when the JVM starts up. You can specify any other function as
static. In fact, you can have a static method and non-static method with
the same name; they'll have different signatures.
So here's what I'd suggest for your prototype:
ResendOrder pr o STATIC extproc(*JAVA:
'com.WMS_BPCS_Integrator.ex-
ecutable.ResendOrder':'resendOrder')
class(*JAVA:'java.lang.String')
o class(*JAVA:'java.lang.String')
dim(2)
And your method definition should look like this:
String static resendOrder(String[] input{
return "gotcha";
}
I just noticed you're passing in a String array (dim(2)) and not two
String's. Of course that's the classic signature for the JVM startup
method: static void main(String[] xx)
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.