Antony Stubbs wrote:
We're developing a Struts application which will be deployed onto Websphere
eventually.
However, I find Websphere very heavy weight do use during development -
publishing seems to take for ever, and seems as thought for many changes it
must be restarted.
What's a common container to use during development that will facilitate the
fastest (computer burden-wise) code, deploy, test, code, deploy, test cycles
etc?
I've tried Tomcat, and that seems to work better, but it still has to be
restarted (well, eclipse (RAD actually) seems to insist on restarting it).
Jetty? And are there any guides out there to guide in setting up the fastest
environment?
Is there anyway to get changes instantaneously viewable aka Grails / Rails
etc?
I will need to setup JNI for the datasource (DB2 and Oracle) in the
container, and even better have the container support j_security_check.
This is in no way Struts specific, but I generally use either Tomcat
with a deployment descriptor set up to support reloading (hot
deployment) of the web-app, or Jetty via the Maven plugin.
Adding a suitably configured deployment descriptor to your app may well
make Eclipse/RAD/whatever use hot-deploy behaviour too, but you'll need
to go through their support channels to confirm that (or just give it a
try :-)
L.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
