Thanks for the response. I am curious about your response as relates to:
I sympathize with your
troubles learning J2EE and application servers that support the
standard.
do I take to this mean the J2EE RI does not adhere to the standard?
Or that Enhydra, IAS, WebLogic 5.1, Gemstone/J also don't?
For example, by a client JAR I mean a java program with a main that
is called via an invocation like
java EJBClient,
where EJBClient class implements the main method and acquires the home
interface for some bean using the JDNI, and then invokes create method
on the home interface to get the remote interface, and then invokes
the remote interface methods to cause the bean instance to do something.
At this point, I have pretty much went thru the procedures step by step
from the URL http://www.znerd.demon.nl/orion-primer/
step-by-step, deployed the application. When I run the URL to launch the
application
servlet, I get a 404 error. Orion logs nothing useful. And this is
apparently (and I maybe
wrong) a supported application since I got at it via the Orion home page, or
link there from).
I have managed to deploy my smoke test (a few session and/or entity beans)
on the following
products:
(1) J2EE RI
(2) Enhydra
(3) IAS
(4) Web-Logic 5.1
(5) Gemstone/J
I had to learn certain things about these servers, but at least when I
followed the documentations
thing eventually worked. It took at most one day to figure out the vendor
idiosyncracies. Two
days into the Orion server, it's not even clear how to perform a structured
shutdown of the server!
java C:/orion] java -jar admin.jar ormi://blazer.youbet.com:8080 admin root
-shutdown
error: javax.naming.NamingException: Lookup error:
java.io.StreamCorruptedException: Caught EOFExcept
e stream header; nested exception is:
java.io.StreamCorruptedException: Caught EOFException while reading
the stream header
So perhaps I put in a little more effort, but it doesn't look good at this
point.
-----Original Message-----
From: Will Glozer [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 08, 2000 3:03 PM
To: Orion-Interest
Subject: RE: Deployment confusions
The FAQ http://www.orionserver.com/faq/ describes how to use the
admin.jar tool to deploy to a remote server.
There is no "command-line method to acquire the client support files
from the Orion server." I'm not even sure what you mean by this,
but if you question is about RMI stubs etc those are all transparently
generated by the server.
I don't know what "a command-line method to invoke a EJB client(s)."
is either. If you are making a client.jar then it is up to you to
make it an executable jar via the manifest Main-Class: attribute.
You are welcome to "take this server off our list", but I have a
feeling that you will have a very hard time finding a better server,
or one that somehow does everything for you. I sympathize with your
troubles learning J2EE and application servers that support the
standard. It is big and complex as enterprise tools tend to be, so
you will need a bit of patience.
Regards,
Will
-----Original Message-----
From: Richard Landon [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 08, 2000 1:16 PM
To: Orion-Interest
Subject: Deployment confusions
I am probably stupid, but....
I still very confused about deployment using Orion. My understanding from
the documentation is that
I must edit the server.xml and add the code. No problem for me as a
developer. But when it comes
to migrating our application into pre-production or production, whoa-nellie,
that ain't going to cut
it. So, here's they same question I posted here repeatedly since yesterday.
I need a command-line method to deploy the ear file once it gets built into
the Orion server.
I need a command-line method to acquire the client support files from the
Orion server.
I need a command-line method to invoke a EJB client(s).
I guess I spend the rest of the day trying to figure it out, and then take
this server off our list.
