Forget the dodos with no backbone who'll advise going with big names. Its a
wonder they aren't using Microsoft. Use jBoss in your test environment and
on your developers boxes. When you understand it, and its running smoothly,
put it in production. If you have problems, then you can purchase a name
brand. When you need more, like clustering and failover, go with a name
brand. I talked to a rep at GemStone the other day with just this
conversation. He wholeheartedly recommended this strategy.
Mica Cooper
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Bill Burke
Sent: Thursday, March 29, 2001 4:47 PM
To: JBoss-User
Subject: [JBoss-user] I need ammo
All,
I need help. I really need some references on who is using JBoss in
production and to what scale. I'm meeting resistence on adopting JBoss
at my company and really need this information to convince the
nervous, uninformed, upper-upper management(CIO types) that this is the
way to go.
Thanks very much in advance,
Bill Burke
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
