Response in-line ...
----- Original Message ----- From: "Frank W. Zammetti" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Monday, November 29, 2004 7:35 PM
Subject: Re: WAR based project layout vs Sun J2SE blueprint layout
We actually have two production environments here... One is a real hosting environment where there are admins in charge of everything. They require nothing but WARs. Then there is another environment that was SUPPOSED to be THE environment eventually, but that plan got nixed. All the apps hosted there are simply installed in exploded form.
Ours run in exploded form too, but only the EAR/WAR ... not all the source etc :-) Our production boxes are just that - a place to install finished, fully-tested applications. You don't need the source there if it works! Heck, you can't do development there. Why have the source?
Even a HUGE webapp is relatively small. Even if it's a couple of megs big (not counting source of course), no big deal.
Yeah, but to some extent it's about what needs to be there too. ... and, by the same token, what doesn't.
The one comment I will make is that the hosted environment takes FOREVER to get anything promoted to prod, whereas the other environment I can do it in a few minutes. And when it's just a JSP change or a new image or CSS change, I don't have to bring the app down, whereas the other environment does (probably not being managed properly, but it is what it is).
I can promote an application to full production status in a day if I really must. Two days is practical without having to run up the food chain too far for signatures.
We take change control very seriously :-) ... but you should see our ratio of changes to incidents resulting from implementations ;-) ... we do fanastic.
We to don't do much in the way of separation of jobs. We have in some instances, but generally it's a couple of guys (or even just one in many cases) doing all the development, front-end and back (and database work as well usually). I don't know, I tend to like that most of the time because I get to do everything, but it certainly becomes obvious on the bigger projects that breaking things up would probably be better.
I wish I could do database work :-( I really do. Databases actually get two seperate teams here: one team architects the model (Data Architects) and the other is in charge of implementing the model and keeping the servers going (the DBAs).
I've seen one or two spots I'd loved to have used a stored procedure - would have worked beautifully - but ... eh ... I hear the DBAs are difficult to set in motion about getting them updated. Mere "mortals" like me don't have permissions to create/modify things of that nature - only data :-(
Our development environment is the desktop - WSAD runing a WSAS 5.0 instance. We have dedicated test boxes we deploy apps to via an web interface. That's really kind of a sterile testbed, but it occassionally gets used for other things too - like if we really need to have multiple machines running the app so we can bounce folks around for some reason. We only get a single dev box, so the other boxes are our workstations. That's a minor annoyance. It works though ;-)
Eddie
-- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com
Eddie Bush wrote:Do people really deploy things to production like this? We generally just publish an EAR or WAR file to the server and keep the source in a versioning system. It seems like pretty wasteful space on a production server to have an application plus all the files that make up the application. ... at least, to me.
'course, God only knows how many apps are running on a single server - I know there are several though - each with their own server instance. There is a seperate (infrastructure) team that deploys apps. Kind of odd though. Even as split up into teams as we are, the developers *still* do the HTML/JSP pages! I can't imagine an environment where they didn't. I don't know if I'd want to. I suppose, to us, all the "development" tasks fit in the "Application Programmer" role.
... kind of helps us maximize the use we get out of production boxes though :-)
Eddie
----- Original Message ----- From: "Vic" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, November 29, 2004 6:21 PM Subject: Re: WAR based project layout vs Sun J2SE blueprint layout
Here is a tomcat specific setup of the app: <Context docBase="/dev3/apps/mds/web" > </Context>
Folder web is much war like! But... next to it in ../mds/src is where src is.
hth, .V
Dahnke, Eric (Company IT) wrote:
Thanks for the response. In this case then, the dev/ folder is presumably under vcs and the layout would be fairly WAR based?
Thx.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0448-1, 11/26/2004 Tested on: 11/29/2004 6:57:36 PM avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0448-1, 11/26/2004 Tested on: 11/29/2004 8:28:17 PM avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
