the web app structure should look something like this(which is really just an
unpacked WAR)
web-app/
*.html, *.jsp, ...
WEB-INF/
web.xml
classes/
I would say that using J2EE architecture and EJB is most useful if you don't have
specific performance needs. When you don't have leeway on performance
you have to bite the bullet and use whatever gives you the performance you need.
Obviously EJB2.0 OR mapping is a huge key, this allows the
It seems that you just need to use the standard structure for your ejb jar and
client app jar files.
The ejb jar file structure is shown in the orion and cmp primers on
www.jollem.com -- and the
application client jar should be structured like this:
app-client.jar
app-client.class
Richard Landon wrote:
I need a command-line method to deploy the ear file once it gets built into
the Orion server.
for this you just put the ear file in the applications directory and put one
line for each ear into server.xml.
example: application name="ip"
