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

Joe,

> Where in the documentation?  I need to take a look at that.
Here is what I have bookmarked in IBM's docs. It is from WAS 4:

http://www-3.ibm.com/software/webservers/appserv/doc/v40/ae/infocenter/was/060501.html

> This is the interesting phrase - "automatically restart".  Restart what?

It depends on what you change.  For JSP's it doesn't restart anything, it 
just picks up the new JSP.  For changes to servlets or supporting JAR 
files, or web.xml it will restart the web module.  I do not think there is 
ever a time it restarts the whole server.

> But I assume that TurnOver isn't free, right?

Correct.

The EAR/WAR thing comes from Sun and the J2EE spec.  It is pretty clear, 
to me anyway, that they were only thinking of it from a "vendor" point of 
view.  Meaning your app vendor delivers you an EAR file, you run a Wizards 
to install it, all is great and simple.  For people actually doing 
development and wanting to make continuous improvements the process is a 
nightmare. 

I wouldn't say we subvert the EAR/WAR process, you still use it to do your 
initial install.  By the way, the EAR/WAR file is simply a 
delivery/packaging mechanism.  The app server just uses it to unpack the 
application it doesn't refer to it after the app is installed.  There is 
nothing in J2EE that says you have to update an existing application by 
doing uninstall/reinstall, that is simply one way that WebSphere 
implements it.  WAS also supports Hot deployment and Dynamic reloading so 
that people that understand their application architecture can deploy just 
the changes.

Mark