You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by David Worms <da...@simpledesign.com> on 2003/02/20 04:27:08 UTC

Plexus location

I haven't looked at plexus for a while and it seems to have move form 
its "zenplex" cvs repository. Does someone know how to get it? thanks.

David


---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org


Re: Plexus location

Posted by Jason van Zyl <ja...@zenplex.com>.
On Thu, 2003-02-20 at 18:26, David Worms wrote:
> Notes for those interested, here is how I build plexus.
>  From there I got jetty to run inside plexus, but stop there. I couldn't  
> load summit.
> 
> Is there any demos/applications using summit already?
> 
> David

This is incredibly wrong and misleading. If you don't know how to use
plexus please don't take guesses and then tell others about your
guesses.

I'm sorry but what you have below is riduculous. If you don't know ask.
If you don't want to dig, don't use it. We're at the point where we are
looking for developers who are trying to make applications and willing
to tweak the core.

Please, please I beg you to get informed.

> - create a "src" directory in plexus-components
> - put "saaj-api.jar" in my classpath (maven should load it instead)
> - execute "maven"
> - build a directory structure such like
>    - bin
>    - conf
>    - logs
>    - webapps
> - create a startup script such like
> CLASSPATH=
> CLASSPATH="$CLASSPATH":../lib/plexus-0.2.jar
> CLASSPATH="$CLASSPATH":../lib/plexus-jetty-1.0-alpha-2.jar
> CLASSPATH="$CLASSPATH":../lib/plexus-manager-1.0-alpha-2.jar
> CLASSPATH="$CLASSPATH":../lib/plexus-messenger-1.0-alpha-2.jar
> CLASSPATH="$CLASSPATH":../lib/plexus-persister-1.0-alpha-2.jar
> CLASSPATH="$CLASSPATH":../lib/plexus-pull-1.0-alpha-2.jar
> CLASSPATH="$CLASSPATH":../lib/plexus-scheduler-1.0-alpha-2.jar
> CLASSPATH="$CLASSPATH":../lib/plexus-summit-1.0-alpha-2.jar
> CLASSPATH="$CLASSPATH":../lib/plexus-velocity-1.0-alpha-2.jar
> CLASSPATH="$CLASSPATH":../lib/plexus-workflow-1.0-alpha-2.jar
> CLASSPATH="$CLASSPATH":../lib/plexus-xmlrpc-1.0-alpha-2.jar
> CLASSPATH="$CLASSPATH":../lib/avalon-framework-4.0.jar
> CLASSPATH="$CLASSPATH":../lib/commons-io-0.2.jar
> CLASSPATH="$CLASSPATH":../lib/commons-lang-1.0.jar
> CLASSPATH="$CLASSPATH":../lib/log4j-1.2.6.jar
> CLASSPATH="$CLASSPATH":../lib/jetty-4.1-rc6.jar
> CLASSPATH="$CLASSPATH":../lib/servletapi-2.3.jar
> CLASSPATH="$CLASSPATH":../lib/jasper-compiler.jar
> CLASSPATH="$CLASSPATH":../lib/jasper-runtime.jar
> CLASSPATH="$CLASSPATH":../lib/commons-logging-1.1-dev.jar
> java -Dplexus.home=../ -classpath $CLASSPATH org.apache.plexus.Plexus  
> ../conf/plexus.xml
> - put all depencies in the lib folder
> - create a plexus.xml config file
> 
> <plexus>
>    <load-on-start>
>      <service role="org.apache.plexus.jetty.ServletContainer"  
> id="jetty"/>
>    </load-on-start>
> 
>    <!--
>     |
>     | Loggers
>     | Sinks
>     |
>     | Directing particular loggers to sinks.
>     |
>     -->
> 
>    <logging>
> 
>      <!-- LoggerManger -->
>      <logger-manager-type>log4j</logger-manager-type>
> 
>      <!-- Loggers -->
> 
>      <logger>
>        <id>root</id>
>        <appender-id>default</appender-id>
>        <priority>INFO</priority>
>      </logger>
> 
>      <!-- Appenders -->
> 
>      <appender>
>        <id>default</id>
>        <type>file</type>
>        <type-configuration>
>          <file>${plexus.logs}/plexus.log</file>
>          <append>true</append>
>        </type-configuration>
>        <threshold>INFO</threshold>
>        <layout>pattern-layout</layout>
>        <conversion-pattern>%-4r [%t] %-5p %c %x -  
> %m%n</conversion-pattern>
>      </appender>
>    </logging>
> 
>    <resources>
>       
> <component-repository>${plexus.home}/components</component-repository>
>      <jar-repository>${plexus.home}/app-lib</jar-repository>
>      <directory>${plexus.home}/conf</directory>
>    </resources>
> 
>    <components>
> 
>      <!--
>       |
>       | Id'd Jetty ServletContainer component.
>       |
>       -->
>      <component>
>        <id>jetty</id>
>        <role>org.apache.plexus.jetty.ServletContainer</role>
>         
> <implementation>org.apache.plexus.jetty.JettyServletContainer</ 
> implementation>
>        <version></version>
>        <configuration>
>          <host>localhost</host>
>          <port>8080</port>
>          <webappsDirectory>../webapps</webappsDirectory>
>          <extractWars>true</extractWars>
>          <stopGracefully>true</stopGracefully>
>        </configuration>
>      </component>
> 
>      <!--
>       |
>       | Anonymous Jetty ServletContainer component.
>       |
>      <component>
>        <role>org.apache.plexus.jetty.ServletContainer</role>
>         
> <implementation>org.apache.plexus.jetty.JettyServletContainer</ 
> implementation>
>        <version></version>
>        <configuration>
>        </configuration>
>      </component>
>       -->
> 
>    </components>
> </plexus>
> 	
> 
> 
> 
> On Wednesday, February 19, 2003, at 09:26  PM, Pete Kazmier wrote:
> 
> >>>>>> David Worms writes:
> >
> > David> I haven't looked at plexus for a while and it seems to have
> > David> move form its "zenplex" cvs repository. Does someone know how
> > David> to get it?
> >
> > Plexus has been moved to the eng.werken.com machine and the repository
> > has been split up into 'plexus-container' and 'plexus-components'. The
> > following CVSROOT will get you to the repos (anonymous password is
> > empty, just hit return):
> >
> >    :pserver:anonymous@cvs.werken.com:/cvsroot/plexus
> >
> > For those of you that aren't familiar.  Plexus is an avalon-like
> > component container runtime.  In its simplest form, Plexus manages the
> > lifecycle of a set of components.  It can be used for any number of
> > things from a web application framework (like Summit) to a runtime for
> > Maven.  Summit is a Turbine-like web application framework that runs
> > within Plexus.  Its basically Turbine but its guts have been turned
> > into components.  Both of which are currently under development. For
> > those interested in Summit, you'll find it in the plexus-components
> > repository.
> >
> > Thanks,
> > Pete
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: turbine-user-help@jakarta.apache.org
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
-- 
jvz.

Jason van Zyl
jason@zenplex.com
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society


---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org


Re: Plexus location

Posted by Pete Kazmier <pe...@kazmier.com>.
>>>>> 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: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org


Re: Plexus location

Posted by David Worms <da...@simpledesign.com>.
Notes for those interested, here is how I build plexus.
 From there I got jetty to run inside plexus, but stop there. I couldn't  
load summit.

Is there any demos/applications using summit already?

David

- create a "src" directory in plexus-components
- put "saaj-api.jar" in my classpath (maven should load it instead)
- execute "maven"
- build a directory structure such like
   - bin
   - conf
   - logs
   - webapps
- create a startup script such like
CLASSPATH=
CLASSPATH="$CLASSPATH":../lib/plexus-0.2.jar
CLASSPATH="$CLASSPATH":../lib/plexus-jetty-1.0-alpha-2.jar
CLASSPATH="$CLASSPATH":../lib/plexus-manager-1.0-alpha-2.jar
CLASSPATH="$CLASSPATH":../lib/plexus-messenger-1.0-alpha-2.jar
CLASSPATH="$CLASSPATH":../lib/plexus-persister-1.0-alpha-2.jar
CLASSPATH="$CLASSPATH":../lib/plexus-pull-1.0-alpha-2.jar
CLASSPATH="$CLASSPATH":../lib/plexus-scheduler-1.0-alpha-2.jar
CLASSPATH="$CLASSPATH":../lib/plexus-summit-1.0-alpha-2.jar
CLASSPATH="$CLASSPATH":../lib/plexus-velocity-1.0-alpha-2.jar
CLASSPATH="$CLASSPATH":../lib/plexus-workflow-1.0-alpha-2.jar
CLASSPATH="$CLASSPATH":../lib/plexus-xmlrpc-1.0-alpha-2.jar
CLASSPATH="$CLASSPATH":../lib/avalon-framework-4.0.jar
CLASSPATH="$CLASSPATH":../lib/commons-io-0.2.jar
CLASSPATH="$CLASSPATH":../lib/commons-lang-1.0.jar
CLASSPATH="$CLASSPATH":../lib/log4j-1.2.6.jar
CLASSPATH="$CLASSPATH":../lib/jetty-4.1-rc6.jar
CLASSPATH="$CLASSPATH":../lib/servletapi-2.3.jar
CLASSPATH="$CLASSPATH":../lib/jasper-compiler.jar
CLASSPATH="$CLASSPATH":../lib/jasper-runtime.jar
CLASSPATH="$CLASSPATH":../lib/commons-logging-1.1-dev.jar
java -Dplexus.home=../ -classpath $CLASSPATH org.apache.plexus.Plexus  
../conf/plexus.xml
- put all depencies in the lib folder
- create a plexus.xml config file

<plexus>
   <load-on-start>
     <service role="org.apache.plexus.jetty.ServletContainer"  
id="jetty"/>
   </load-on-start>

   <!--
    |
    | Loggers
    | Sinks
    |
    | Directing particular loggers to sinks.
    |
    -->

   <logging>

     <!-- LoggerManger -->
     <logger-manager-type>log4j</logger-manager-type>

     <!-- Loggers -->

     <logger>
       <id>root</id>
       <appender-id>default</appender-id>
       <priority>INFO</priority>
     </logger>

     <!-- Appenders -->

     <appender>
       <id>default</id>
       <type>file</type>
       <type-configuration>
         <file>${plexus.logs}/plexus.log</file>
         <append>true</append>
       </type-configuration>
       <threshold>INFO</threshold>
       <layout>pattern-layout</layout>
       <conversion-pattern>%-4r [%t] %-5p %c %x -  
%m%n</conversion-pattern>
     </appender>
   </logging>

   <resources>
      
<component-repository>${plexus.home}/components</component-repository>
     <jar-repository>${plexus.home}/app-lib</jar-repository>
     <directory>${plexus.home}/conf</directory>
   </resources>

   <components>

     <!--
      |
      | Id'd Jetty ServletContainer component.
      |
      -->
     <component>
       <id>jetty</id>
       <role>org.apache.plexus.jetty.ServletContainer</role>
        
<implementation>org.apache.plexus.jetty.JettyServletContainer</ 
implementation>
       <version></version>
       <configuration>
         <host>localhost</host>
         <port>8080</port>
         <webappsDirectory>../webapps</webappsDirectory>
         <extractWars>true</extractWars>
         <stopGracefully>true</stopGracefully>
       </configuration>
     </component>

     <!--
      |
      | Anonymous Jetty ServletContainer component.
      |
     <component>
       <role>org.apache.plexus.jetty.ServletContainer</role>
        
<implementation>org.apache.plexus.jetty.JettyServletContainer</ 
implementation>
       <version></version>
       <configuration>
       </configuration>
     </component>
      -->

   </components>
</plexus>
	



On Wednesday, February 19, 2003, at 09:26  PM, Pete Kazmier wrote:

>>>>>> David Worms writes:
>
> David> I haven't looked at plexus for a while and it seems to have
> David> move form its "zenplex" cvs repository. Does someone know how
> David> to get it?
>
> Plexus has been moved to the eng.werken.com machine and the repository
> has been split up into 'plexus-container' and 'plexus-components'. The
> following CVSROOT will get you to the repos (anonymous password is
> empty, just hit return):
>
>    :pserver:anonymous@cvs.werken.com:/cvsroot/plexus
>
> For those of you that aren't familiar.  Plexus is an avalon-like
> component container runtime.  In its simplest form, Plexus manages the
> lifecycle of a set of components.  It can be used for any number of
> things from a web application framework (like Summit) to a runtime for
> Maven.  Summit is a Turbine-like web application framework that runs
> within Plexus.  Its basically Turbine but its guts have been turned
> into components.  Both of which are currently under development. For
> those interested in Summit, you'll find it in the plexus-components
> repository.
>
> Thanks,
> Pete
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org


Re: Plexus location

Posted by Pete Kazmier <pe...@kazmier.com>.
>>>>> David Worms writes:

David> I haven't looked at plexus for a while and it seems to have
David> move form its "zenplex" cvs repository. Does someone know how
David> to get it?

Plexus has been moved to the eng.werken.com machine and the repository
has been split up into 'plexus-container' and 'plexus-components'. The
following CVSROOT will get you to the repos (anonymous password is
empty, just hit return):

   :pserver:anonymous@cvs.werken.com:/cvsroot/plexus

For those of you that aren't familiar.  Plexus is an avalon-like
component container runtime.  In its simplest form, Plexus manages the
lifecycle of a set of components.  It can be used for any number of
things from a web application framework (like Summit) to a runtime for
Maven.  Summit is a Turbine-like web application framework that runs
within Plexus.  Its basically Turbine but its guts have been turned
into components.  Both of which are currently under development. For
those interested in Summit, you'll find it in the plexus-components
repository. 

Thanks,
Pete


---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org