Originally posted by Solo Chiang:
Hi to all
In another words, they don't need to do any real deployment, since their work
I think you've just answered your own question. WebLogic is fairly heavy, so the less starting, stopping, and redeploying people have to do, the faster they can spin through the code/compile/test cycle.
On the other hand, becoming over-dependent on the internal deployment infrastructure of WebLogic is a little dangerous, since if they change it, the whole project structure will have to be re-evaluated.
I do something similar with
Tomcat, however. The difference is that Tomcat can be configured to run apps that are installed outside of Tomcat itself, so I just point Tomcat to the part of the project where I build my WAR. It's a fully-sanctioned way of configuring Tomcat, so I have almost no risk that future releases of Tomcat will find it disagreeable.