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

> From: Mark Phippard
>
> Did your tone just get a little harsh or I am I reading something into it?

Nope, not harsh.  Just questioning.  And we've got two discussions giong
here - basic web application design and WebFacing web application design.


> > How often is code ENTIRELY stable, Mark?  Be realistic.
>
> You made it sound as though this code is changing infrequently, for
> example, I consider JT400 to be "stable".  You get periodic new releases.
> If you are only changing your code once a month packaging it into
> a JAR is
> not a hardship.

No, I'm talking about the primary code base of an applciation which should,
in my mind, be part of a JAR file.


> Just talking about what I have observed.  I do not believe I
> passed myself
> off as an authority.  Please send me links to those white papers
> though. I
> do not believe it would be even remotely possible for the JIT process to
> be effected by JAR or no JAR.  I do think it could effect class loading
> however, which is also a performance consideration.

The one I primarily remember is here:

http://www-1.ibm.com/servers/eserver/iseries/service/itc/pdf/top10wasperform
ancetips.pdf

It may be out of date, but it specifically states in point 6 to JAR your
servlets for loading AND optimization, and why.  The recent move from static
compilation to HotSpot type compilers has definitely reduced that particular
trend, since JIT compilers know more about the state of the machine than do
the static compilers.  Static compilers (such as CRTJVAPGM) benefit greatly
from  JAR files while JIT compilers do not.


> I may have been misunderstanding all along.  Are you saying you
> would like
> the .class files that are created for your JSP's to all be bundled in a
> JAR?  I am not aware of anything that would do that.  I am not sure it
> would even work if you did it manually, because the JSP compiler engine
> would probably just see the JSP as not having been compiled.  I could
> definitely be wrong on that though.

No, I think a good application design is that everything EXCEPT the JSPs be
bundled in JAR files.


> I follow an MVC approach to design.
(...)
> My controller layer in web applications is Struts.  This leads to a lot of
> little classes that go go out and get data from the model layer and
> present it in the view layer.

Okay, I understand your situation.  I don't use Struts because I have my own
controller layer which is completely UI independent, as well as completely
dynamic.  A small definition file is read in when a program is first
accessed, which defines the interaction between the program and the UI; this
takes the place of all your little classes.  A view layer thens converts
that to whatever form I need - 5250 emulation style JSP, web style JSP, or
pure HTML.  It could just as easily do XML, which could talk to a thick
client or be exposed as a web service.

Joe