In relation to this - up until now I have been using ant to build/deploy my
EAR file. Works fine, but slow. So I've tried to get Orion working live
against my source code.
A couple of questions:
How do EJB's fit into all of this? At the moment, I'd actually prefer to
keep them in the EAR file, but I'd like to know what the options are. How
does the web-app link to the EJB's?
I have a directory structure identical to the WAR file I'm deploying, except
with .java files instead of .class files, so it's just a matter of pointing
to that, right? Problem is, this is on a different drive (network) - how do
I get Orion to work from there? In my default-web-app.xml I'm not sure what
to put for 'root' (or 'name' or 'application' for that matter!). Something
like:
<web-app application="myapp" name="myapp-web" root="file://p:/myapp/war/" />
<web-app application="myapp" name="myapp-web" root="p:/myapp/war/" />
Doesn't work?
----- Original Message -----
From: "Kevin Duffey" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Friday, July 14, 2000 2:35 AM
Subject: RE: Creation Of WAR Files?
> I believe Orion has a GUI tool that creates a WAR for you, but that is
> beyond me. When I am developing, I don't WAR up the dir. I keep it
expanded.
> You point to the WAR directory structure in default-web-site.xml in the
> /config folder. Just read up on that and you should be set to have a WAR
> file for development. Then you can JAR up the dir:
>
> jar cvf myfile.war root-dir
>
> That should jar up your entire www structure, including the WEB-INF folder
> which has
> /classes - the compiled code of your app
> /lib - the .jar and .zip libraries loaded for you by Orion (as per the
> servlet 2.2 spec)
> web.xml - the descriptor that explain to Orion how to run.
>
> Anything in /classes automatically becomes part of the classpath, that is
> part of the servlet 2.2 spec and should work on any servlet 2.2 container.
> Anything in the /lib folder should be loaded by the application server
> automatically and become part of the classpath as well. We put jdbc.zip
(for
> Oracle 8i) there, along with activation.jar, mail.jar, jasp.jar, and other
> .jar files we need. At runtime they are automatically seen by your app (in
> the import statements of your classes). Nothing special to do.
>
> Orion has a very kewl feature that allows you, during development, to
point
> to a "source" directory that matches the package structure output of your
> compiled classes. It then checks the source dir for changes (time-date)
> compared to the .class file it was compiled in to. If there is a change,
it
> recompiles and reloads the web-app for you. This allows you not to have to
> shut down and restart orion every time you make a code change. Most app
> servers support this for classes in the /servlets dir, and generally that
is
> javabeans and servlets. Orion (and Resin does this too) will reload the
web
> app if any classes changed. The only downside is that it can take a few
> seconds for it to check the files. I believe its faster than restarting
> though.
