RE: framework question

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

> From: NGay@xxxxxxxxxxxxx
> 
> Aaron,
> 
> Hence we are
> considering rewriting all the business logic into Java code where it
will
> be nicely organized, use proper data types, inheritance and so on.

Java is good for many, many things, but one thing it is NOT good for is
programming business logic.  Inheritance is perhaps the single most
overused (and misused) feature of any language ever designed, and it
almost NEVER applies in the business world.  Business application make
far better use of composition than inheritance in well over 90% of the
cases I've ever looked at.  Try to come up with 10 places where
inheritance (especially Java's single-parent inheritance model) makes
sense.

Java is horrid at executing conditional logic based on database flags,
and is also terrible at allowing quick changes to the logic for a
specific problem, both of which are required in real-world business
applications.

There is a reason why nobody has really made much headway in creating a
generic set of business objects: because such a goal is very hard to
achieve.


> Then we
> would replace the exisiting 'fat' 5250 screens which currently have
all
> the
> business logic mixed in by 'thin' 5250 screens which are nothing more
than
> a UI layer calling the Java business logic in the background to do all
the
> work.

Instead, I think the proper way to go about things is to create a
JSP/servlet front end to your existing applications, then begin
rewriting them into servers as need be.  Some programs may never need to
be rewritten: for example, do you REALLY need client/server access to
your chart of accounts master?  Probably not.

Anyway, my .02.

Joe