All JPO methods invoked from MQL or the ENOVIA Studio Customization Toolkit
must adhere to two signatures. These signatures are:
int (Context, String [])
and
Object (Context, String [])
Where any derivation of Object can be substituted for
"Object". Any methods not called from MQL or the ENOVIA Studio Customization Toolkit can have any signature. So in general, some methods will be written
to the signatures given above and then these methods will process the
incoming argument list and call on other methods using signatures that
are specific to the task being accomplished.
JPO constructed objects live until the current transaction is ended.
This means that a JPO constructor need only be called once inside a transaction.
Then other methods of the JPO can be executed off the cached object.