Personally, I don't use PCML, I use the standard toolbox classes.  But I
don't know of any seven-parameter limitations except on service programs.
On the other hand, dates are still tough, though not impossible: you define
the parameter as an array of bytes and then use the DateTimeConverter class
to convert the date to a usable value.

Anyway, I suspect your problems arise from your application architecture;
your service programs have lots of small methods that return values, much
like getters in an OO environment.  Me, I pass data structures between
programs; it works much better.  I never have to worry about having too many
parameters, and I can pass structures inside of structures with no problems.

Joe


From: albartell

The last I used Java's integration to RPG, specifically PCML, I made some
good progress but then was stopped by a brick wall.  The brick wall was a
limitation on the number of parameters that could be passed (i.e. seven
parms max at the time), the lack of being able to pass date data types,
and
the lack of being able to pass back anything other than an int in the
passback parm of an RPG sub procedure.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.