|
Joe said: > ...perhaps you might try deploying a few net changes > and see what happens. On my model 270, deploying > a single-line fix ON A TRIVIAL APPLICATION took > 20 minutes, most of which time the application server > was unavailable. If you think this is acceptable from a > production standpoint every time you need to deploy > a hot fix, then you come from a different environment than I do. I agree that this is unacceptable. But I have deployed many hot fixes, similar to the one line oopsie you mention, and have never had to tear WAS or Tomcat down to do it. Nor did I have to use a 3rd party tool to deploy: I wrote simple CL commands to MOV the objects from hither to yon. It could also be done with DOS batch files or a *nix or QSH script. As you have mentioned in the past, one DOES need to understand the directory structure used by J2EE, which seems to be identical for WAS 4+ and Tomcat 4+. Discovering the file structure is not at all difficult in my opinion, even without looking at any documentation. I advise beginners to create a teeny-tiny application, WAR it up and deploy it, then look at the results in the file system. Should you be FORCED to do this? Well, I'm on the fence on how to answer that. On the one hand, I'm a programmer, and it's my livelyhood to understand as much about my little computing universe as I possibly can. On the other hand, I realise that not all programmers share my personal view on the matter. Today, it seems to me that the web universe is still pretty young, and people who want to play here should be more propellerhead than the proverbial average programmer. --buck
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.