That's horrifically bad advice from your Java developers. Nothing stops the app server from starting a second instance of the servlet and that defeats the synchronization.
That type of business logic can't be done correctly without utilizing the database's concurrency controls (either raw JDBC/SQL or calling an RPG program via JDBC or PCML).
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Nathan Andelin
Sent: Friday, October 08, 2010 2:45 PM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Microsoft .NET frontending IBM i
From: Richard Schoen
Once a company goes with Java, PHP, etc... RPG
is really no longer needed and neither is OS/400 ...
Are you sure? In my office, we were just the issue of deleting courses from our
course catalog. What if child records exist? Course Prerequisites? Course
Objectives? What if a class has already been scheduled that taught that
"course"?
Do you want to move all that investigation and decision making down to the
servlet?
In our scalability discussion, Java experts were just suggesting that developers
might need to serialize methods that implement business rules like that. The
application server won't do it for you. Are you sure you want to move that type
of processing to the servlet?
-Nathan
midrange.com
