This is the same point I have been hammering to Orion for a while. Orion makes a
wonderful product, but how do those outside of the Orion world know that? If you
never heard of the state of Hawaii, and I told you a hundred years ago it's a great
island to sail to, would you believe me? If I printed up some descriptive literature,
and put pretty pictures in them, would you be inclined to take the trip? So what does
Orion need? A good, organized manual, with topic headings, like the jboss manual
provides. Detailed worked out examples, like the site www.jollem.com provides. Go to
a site like Jrun or ewave, download the documentation, and review it. Don't write the
doc yourself, but hire a good tech writer. If you need one, I can recommend one from
my writing class that can make the Orion doc read like "Gone with the Wind". Make
the documentation so simple, I could give it to my janitor and he will say -- J2EE,
yee haw!
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 23, 2001 1:30 AM
To: Orion-Interest
Subject: EJB Clustering -- ANYONE? [Urgent!]
A better description of Orion as a product!
I have dedicated a lot of time of testing things that both work and does
not seem to work, for example JMS and otherthings. The feature list on the
frontpage is accordingly to "thin". And yes I have been reading the
mailing list, but is not easy for beginners.
So, some decsription, characterisation (data sheet) or whatever of the
product, that tells the user or byuer what they get and what the
orionserver can handle.
And as pointed out before, the documentation could be better (sorry Magnus,
very general). Have you seen the new documentation for JBoss.
/Theis.
