For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 5 replies, 2 voices, and was last updated 20 years, 10 months ago by
.
-
Posts
-
Adam,
If your question seems to be a generic deployment strategy question, not necessarily related to MyEclipse, is this correct?Yes, the issue is essentially a deployment strategy problem. However, since we rely on the MyEclipse environment, it is important for us to find a solution that works alongside with MyEclipse’s integrated deployment system instead of circumventing it, if possible.
If you wait for Version 4.0.1 and then upgrade (Be sure you are usin Eclipse 3.1 final GA release), I might even suggest all of you using an exploded EAR deployment to your app server with the “Overwrite” setting turned on… however this will still overwrite the JNDI file which the app server will most likely reload anyway but it may not… that coudl be something to try, otherwise I would honestly suggest you all stick to your own installs of the app server even on your ulocal machines and just have a central beta version of your app that is handled by one person every day to update it at set times of the day with the current code snapshot. Having multiple people deploy to the same app on the same server is never a good idea… most tools don’t support it because most app server don’t support/expect it.
Thanks for the suggestion re: 4.0.1, I will give that a shot when it’s released.
In the meantime, we will probably go with your idea of using local appserver instances with a centralized snapshot deployment on our staging server. Currently, we’re using JBoss so this is feasible, but if we later decide to move to a commercial appserver, this configuration may not be financially feasible if appservers are being licensed on a per CPU basis. Is this also how the “big dogs” do it? I’m curious to know how large-scale J2EE projects with large development teams have projects and appservers organized.
You’d be surprised how differently the “big dogs” do it, the solutions are as variable as any set of small teams. I just happen to know another of our large customers uses a local-central organization like I proposed and it works really well for them, every night before he leaves their maintainer updates the snapshot on the production (beta) server and that is what the QA team gets to play with then after everything is kosher that copy gets deployed to the production servers.
As far as Jboss/commercial/etc, unless you guys go making code that relies heavily on app-server specific extensions you should be ok to keep JBoss as the dev installs and then have your commercial app server on the production beta and production servers. You might run into a few hickups, but the worst case scenario is that you end up writing even better server-agnostic code 😉
