RE: Porting Java applications from the 400 (was: SQL update/insert for a string contain " ' ")

I think for AS/400 community, Java is a communicator b/w as/400 and HTML,
just pass parameters back and forth to HTML, using RPG/Cobol stored
procedures or direct call to RPG/COBOL from Java. I don't see compelling
reason to do a lot of programming within Java if my application is on AS/400
and written in RPG/COBOL and I think thats the case in most of the AS/400
enviornment.

You can find 100 good as/400 RPG programmers for less money compare to 1
good OO java programmer :-)



-----Original Message-----
From: Joe Pluta [mailto:joepluta@PlutaBrothers.com]
Sent: Thursday, October 04, 2001 10:50 AM
To: java400-l@midrange.com
Subject: RE: Porting Java applications from the 400 (was: SQL
update/insert for a string contain " ' ")


> -----Original Message-----
> From: Buck Calabro
>
> Yes indeed, but that presupposes that either the programmer is experienced
> enough to plan ahead for this or the design specifies multiple database
> access.  Would a new Java programmer really design her code this way?
> Especially, would a procedural programmer moving to Java think
> this way?  I
> bet they know that they should, but DO they?

They would if they were trained by me <smile>.  In my classes, I stress the
fact that Java is NOT a procedural language, that it's an OO language, and
that you need to think OO to take advantage of it.  Writing procedural code
in Java is like teaching a pig to sing: it doesn't accomplish much, and it
annoys the pig.

The thing I've found during my years of teaching, though, is that once a
programmer is introduced to these concepts, they're very receptive.  Why?
Because they make sense.  It's not that programmers can't understand OO
concepts, just that they've never seen them.  Once they see them, they tend
to eat them up.  There is a certain percentage of folks who will never make
the leap, but that number is surprisingly small.  I've taught classes full
of mainframe COBOL folks, and, after some initial culture shock, they loved
it.  Why?  For two reasons:

1. You only write things once
2. You only debug things once

For COBOL folks especially, not having to type out all that stuff again,
simply being able to call a method, was definitely a GOOD THING.

Joe

_______________________________________________
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
mailing list
To post a message email: JAVA400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l
or email: JAVA400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.