Gotcha. So you're basically saying that if another language requires any
learning, then you don't want it in your environment.

That's a big stretch of what I said. You are just fishing for argument.

Not sure how you're going to incorporate things like Ajax, and of course
PHP is right out of the question. But okay, that's your world.

AJAX can be used with Java or RPG but can't replace them (nothing new to
either of us here). You don't need AJAX to have a solid web app. If you
want some cool-ness then you could weigh the time it would take to invest
vs. what you would gain back (classic ROI). The same is true for the JSP
thin layer model. You need to weigh the cost of introducing that into your
shop. You need to weigh the fact that you will need to maintain a servlet
engine (i.e. Tomcat/Websphere), knowledge of JDK/JRE's, knowledge of Java,
knowledge of Java IDE editor, knowledge of Java in general, train your
helpdesk to take Java/Tomcat trouble tickets, re-work your CMS to facilitate
Java objects, send your staff to training concerning Java, the list goes on.

Introducing a new language that is not native (i.e. RPG, CL, C, COBOL, etc)
to the i5 can double your work in many areas, and being that this model is
tightly coupled, the distribution of Java and RPG changes needs to work
quite seamlessly including if the install fails it needs to be appropriately
backed out.

With that said I would say PHP is an easier option for RPG programmers to
gulp down, though you have many of the same issues described above because
of the new language introduction.

Concerning your comments about EGL - does it use PCML to interface with RPG?
I think I asked this before but I don't remember the answer I got.

Aaron Bartell
http://mowyourlawn.com


-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Joe Pluta
Sent: Monday, June 04, 2007 11:56 AM
To: 'Web Enabling the AS400 / iSeries'
Subject: Re: [WEB400] Windows vs i5/OS as a platform

From: albartell

We will just have to agree to disagree. Adding Java to an RPG
programmers environment simply isn't as easy as you make it out to be
(in my experience).

Gotcha. So you're basically saying that if another language requires any
learning, then you don't want it in your environment. Not sure how you're
going to incorporate things like Ajax, and of course PHP is right out of the
question. But okay, that's your world.


Like I said (paraphrasing here), if the thin JSP layer simply received
the RPG data from the controller and built the screen based on it then
this architecture is much simpler. Of course that would warrant the
passing of meta data with the data, but done right could produce a
pretty cool framework (one that I am working on in the desktop
environment) that is easier to build initially and maintain after the
fact.

That's exactly what EGL does: you define the data and the metadata
separately from the business logic, and then you paint the screen by
dropping the data onto a page using a WYSIWYG designer.

Frameworks that magically build the UI based on assumptions about the data
are cool as well. But again, that's what I do for a living, so I know full
well the down side to that particular approach, which you usually hit
roughly the first time you show a generated screen to the end user and they
say, "But I want that field HERE."

Joe

--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list To post a
message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/web400.


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.