Re: Installing a web change (was: importing a rpg orsqlrpg)

> From: Buck Calabro
>
> Neither does WebFacing.  I updated many individual panels without
> having to
> restart the web module.  In my "development/test" mode, I would re-face,
> export as a file system mapped to the iSeries and then run a CL program to
> move the newly deployed objects into the appropriate WAS directory tree.

Um, that's not WebFacing.  That's WebFacing plus Buck Calabro's custom CL.
So, everybody who uses WebFacing has to basically learn the tool to the
degree you did, then write a custom CL program to move the objects around.
And heaven forbid the directory structure should change.

You consider this acceptable for development tool, I do not.


> In PSC/400, that would mean replacing
> the JSP and XML together.  If we managed to replace the JSP, then
> a request
> comes in and served, the XML is out of synch, not having been
> replaced yet.

Not true.  The XML is only loaded when a program is first run for the life
of the app server, or after a reload.  Synchronization is simple in
PSC/400 - replace the XML first, then the JSP.  Flip the application reload
switch.  Done deal.  The JSP BY DESIGN will not be served until the XML is
reloaded.  It's a simple matter of taking the time to do it right.


> This problem is common to all multi-component applications on
> every platform regardless of vendor.

Only if the vendor doesn't take into account real development practices.
If, on the other hand, the vendor actually understands the requirements of a
production environment, they can develop the tool so that the programmers
are productive BECAUSE of the tool, not DESPITE it.

I'm sorry, Buck, but I consider your expectation level for WebFacing to be
extremely low - closer to a Microsoft product than an IBM product.

Joe