I just joined a company and figured out their "standard" eclipse configuration really make my jaw hit on the floor.
They have one J2EE application, which contains 3 web module, 1 ejb module. In the project I worked before, we usually have 3 dynamic web projects for these 3 web modules, 1 ejb project for this ejb module. And another J2EE project which defines which modules is included in this project.
But in this company that I just joined, they have a big fat J2EE project and Dynamic Web project pointing to the same directory UNDER their weblogic installation folder. And this two projects are actually pointing to the same directory. In another words, they don't need to do any real deployment, since their work is done right under server installation directory.
Would somebody could give me a more systematic explaination why they are not doing things in the right way?
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.
Sometimes the only way things ever got fixed is because people became uncomfortable.
If you look closely at this tiny ad, you will see five bicycles and a naked woman:
Free, earth friendly heat - from the CodeRanch trailboss