Re: More RPG/Java Questions -- RPG400-L

Brad,

Good points. My first two errors were typos because I
miss keyed something that I could have generated. I am
using JDOM to support XML parsing in RPG. That is a
pretty strait forward API so not that bad. I already have
a few dozen Prototypes that support things like converting
a string buffer to a string. Your argument that an RPGIV
program should not have a lot of Java embedded is a
good case for the Code/400 macro.

I am doing this as an experiment. I would attempting to
create a simple interface for RPG programmers to use
when they need to create an XML document. Right up your
eRpg alley actually. I want to shelter the RPG programmer
from the JDOM API.

Yes it could be a Java App, but that cuts out about 90%
of AS/400 shops. I think there are a lot more V5R1 shops
than there are shops with Java programmers. I intend to
publish all of this as open source at:

http://iseries-toolkit.sourceforge.net

The long range goal is to give strict RPG shops access to
the powerful publishing capabilities of Cocoon and other
Java based products.

David Morris


>>> brad@bvstools.com 12/14/01 10:58AM >>>
Explain "define all of those prototypes"

RPG will need some what to know the struture of the method
you plan on using.  Without a prototype, how would it know
what you're trying to do?  Same with ILE subprocedures.

If you're using a lot of Java methods in RPG, then I would
question why you're not using one or the other only.  Is the
Java method doing something that could be just as easily
done in RPG, or could it be a Java app alltogether?

Or are you just playing around with the new feature?

Brad
www.bvstools.com

On Fri, 14 Dec 2001 09:54:19 -0700
 "David Morris" <David.Morris@plumcreek.com> wrote:
> Group,
>
> While playing with Java some more, it seems strange that
> you have to create a prototype for every Java method.
> That
> really limbers up the fingers, but seems avoidable. Do I
> really have to define all of those prototypes?
>
> One way to reduce some of this burden would be to
> generate
> a huge prototype that defines all possible methods in a
> jar or
> the java runtime. The names are certain to get out of
> hand and
> I don't know of any way to like(protype) that actually
> created a
> prototype definition. Using names like could just see
> using code like:
> com_plumcreek_log__getLogger$org_apache_log or
> org_apache_logger__debug$void$java_lang_String
> Precompiling would be an option, but the
> RPG compiler is not really pre-compiler friendly.
>
> Maybe a Code/400 Function that used reflection to build
> these
> on demand? Other ideas?
>
> David Morris

Bradley V. Stone
BVS.Tools
www.bvstools.com