On Dec 31, [EMAIL PROTECTED] quoth:
> As the person who has been ultimately responsible (blame-wise anyway) for
> the success or failure of each of those five projects, I would bet it all
> on JBoss all over again if I had to.
Sorry to reply to my own message but I realized that the above statement
didn't read quite right. What I meant was that the *Technical*
success/failure of the system was ultimately my responsibility and I would
be the one who is held responsible for any *technical* failures. As such
in each case I needed to select the technology which provided the greatest
chance of success. Important issues are ease of development, stability in
deployment and (of course) cost. No system development project (beyond the
very trivial ones) are without signifigant problems and there are always
plenty to go around. Anyone who says otherwise is at best ignorant and at
worst trying to sell you something.
In the interest of sharing the bad news along with the good news, here is
my biggest issue with JBoss in a production environment:
JBoss frequently is updated--this is a good thing. However the bad thing
for *production* use is that not enough (read: any) effort is made to
manage transition smoothly for users. This means your production
environment will lag behind the head of the curve. In our experience
between 1 and 3 versions.
As I'm sure you all know, the business cost of a production server
software upgrade is more than signifigant due to downtime and risk. As of
now there is no part of the JBoss project which attempts to mange or
mitigate essential changes for upgrades. It is up to you to not only test
but also develop the upgrade procedures. Configuration files changed
signifigantly between different BETA versions and 2.0 and from what I've
seen, there appear to be backward-incompatable changes being introduced
into 2.1. This was a huge problem for us.
Obviously anything I say I may be badly worded or mistaken, but what I say
is the truth as far as I know it and reflects my own personal experience
with JBoss as colored by my past experiences with various other vendors
and technologies. I'd be glad to communicate directly with anyone
seriously evaluating JBoss for a commercial production environment and
provide answers to more detailed questions regarding JBoss, my team's
experience with it and my professional background (the basis for having
the opinions I do).
For the good of the JBoss community (and my own inbox) anything general or
inspecific should probably be directed to the list for better, faster
answers and everyone's education. I'm not the only user, just one of the
many, many happy ones.
C=)
P.S. A more direct email address may be found at the bottom of my sexy
web page (http://www.technocage.com/~caskey/) I don't use it on email
lists for obvious reasons.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
