I've designed, wrutten and implemented and EJB app
using Orion AND Weblogic (It sounds like your
situation: we needed to support Weblogic because many
potential clients would already have it in house, but
wanted a cheaper alternative it was possible). For my
client's needs Weblogic provided no additional
benefit, and had some disadvantages (e.g. non-standard
deployment). Orion definitely worked out better for
me, for my client, and for their clients.
I would say that, what you read on the mail lists not
withstanding, Weblogic's support is pretty good; it is
one of the things you're paying for. They also do a
good job of providing non-standard value-added
features (which may or may not be a good thing.)
If your project is not using the latest bleeding edge
features, however (meaning it is using features that
have been in Orion for a while, getting beaten up by
lots of people), and you have more than a passing
knowledge of EJBs, then you won't NEED a lot of
extensive vendor support. Every time we had a problem
with Orion, we always got answers from the EJB mailing
list or this mailing list (it was never an Orion
problem; it was the subtleties of JMS that were
tripping us up).
My suggestion to your boss, to minimize project risk:
1) avoid bleeding edge technology (it will break in
unexpected ways)
2) avoid exotic implementations (use an OS and version
that a lot of people have used, on hardware a lot of
people use; you will not differentiate your product by
having the latest version of AIX)
3) Don't spend a LOT of money for services that you
won't use, since you'll be reading the Orion and EJB
mailing lists every day anyway.
4) Use Orion
5) Buy/lease some of the hardware you'll be
implementing on, and run your target os on it now;
start testing on it as soon as you can. You don't
want to uncover a bug in the JVM for your os during
implemetation week.
6) Avoid similies like the plague
just my 2 cents
LHCommons
--- Julian Richardson <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> I'm trying to collect together reasons for chosing
> Orion over other app
> servers - our company's been doing a lot of research
> into EJB technology
> over the last few months and currently the favoured
> choices seem to be JBoss
> and Weblogic.
>
> I can understand JBoss as a target environment -
> after all it's free. But I
> haven't seen a good case (yet) for using Weblogic;
> as far as I know it's
> pretty expensive and support actually seems a little
> lacking from what I've
> heard from others. From what I know it is pretty
> feature-rich though.
> Anyway, there's a chance for using Orion in
> preference (or at least as
> another official environment) given a solid list of
> reasons...
>
> Any ideas would be appreciated - performance,
> scalability, standards
> adherance, reliability, cost, platform availability,
> support, documentation
> quaility etc. etc. (I've been using it for a couple
> of months now and
> haven't had any trouble other than the usual
> learning 'glitches' :-)
>
> cheers
>
> Jules
>
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35
a year! http://personal.mail.yahoo.com/
