>>>>> David Worms writes:
David> Notes for those interested, here is how I build plexus. From
David> there I got jetty to run inside plexus, but stop there. I
David> couldn't load summit.
[snip]
The Maven Plexus plugin is your friend ... It'll build you a Plexus
runtime from which you can just type bin/plexus.sh. The runtime
includes a shell script to start up the container, all of dependencies
for Plexus, components that your configuration file references, and
dependencies for those components. Note: 3rd party components aren't
included yet automatically, t manually copy mine into the runtime
directory via a Maven postGoal.
Once the runtime is assembled, you just need to start the shell script
and that will start up the container as well as any <load-on-start>
components in your Plexus configuration file. You'll need to tweak
things a little bit as the plugin is still a bit rough around the
edges (as I hinted above). However, I've been using Plexus for about
two months as my component container and its been working out very
well.
I also use Summit for my application's web interface. The application
is not web-centric, its been designed to easily have a swing and
xml-rpc based interface as well, which is one of the reasons I prefer
to have Plexus as my container vs some Servlet container in which I
load Plexus. Instead, once you have a Plexus runtime going, you just
add a ServletContainer component to your Plexus config file (I'm using
the Jetty component already built by Jason, I believe Dan is using
Tomcat). Then, as part of my Maven postGoal I deploy my war file to
the plexus runtime directory along with the Summit deps.
Setting up Summit is a bit more difficult at the moment, I know Jason
is working on enhancing the Summit plugin in Maven (which I'm not
using at the moment) to help automate the process. However, you can
run Summit if you are a bit adventurous. Here is the portion of my
web.xml file that you need for Summit:
<servlet>
<servlet-name>poolserver</servlet-name>
<servlet-class>org.apache.plexus.summit.Summit</servlet-class>
<init-param>
<param-name>configuration</param-name>
<param-value>/WEB-INF/conf/summit.xml</param-value>
</init-param>
<load-on-startup>10</load-on-startup>
</servlet>
Then this is my summit.xml file:
<summit>
<applicationViewsDirectory>/WEB-INF/app-views</applicationViewsDirectory>
<defaultApplicationView>poolserver</defaultApplicationView>
<applicationViews>
<applicationView>poolserver</applicationView>
</applicationViews>
</summit>
Then you'll need a Summit view configuration file which is basically
another Plexus config which defines the components used by Summit
(things like Resolvers, Renderers, the Pipeline). An example config
can be found in the summit repo in src/test-conf/plexus.conf. This
summit view configuration file is stored at this location on my
system: WEB-INF/app-views/poolserver/plexus.xml.
Thats about it, just be aware that both Plexus and Summit are still
under development.
Have fun.
Pete
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
