Re: Using Lenya Access Controller as an isolated component

[Torsten Schlabach]

Michi,

> There were suggestions that we offer Lenya as a jar, whereas I think we
> should go one step further and offer the various components as jars if
> possible (Access Controller, Workflow, ...) because this would allow to
> re-use Lenya also within other application and not just within Lenya
> itself.
This is a brilliant idea which I definitely support! It would also allow 
a clear separation of editing and rendering components and might leed to 
being able to take a vanilla Cocoon and just add the necessary 
components for rendering Lenya content. This has often been asked for in 
real world production environments.

Regards,
Torsten


Michael Wechner schrieb:
Hi

I am currently trying to use the Lenya Access Controller as an isolated 
component.

I have managed to compile it with the following dependencies, which 
might be of interest to you:

  <path id="classpath.lenya.net">
    <pathelement 
location="/home/michi/src/apache/lenya/trunk/build/lenya/webapp/WEB-INF/lib/log4j-1.2.11.jar"/> 

  </path>

  <path id="classpath.lenya.util">
    <pathelement 
location="/home/michi/src/apache/lenya/trunk/build/lenya/webapp/WEB-INF/lib/log4j-1.2.11.jar"/> 

    <pathelement 
location="/home/michi/src/apache/lenya/trunk/tools/jetty/lib/servlet-2.3.jar"/> 

    <pathelement 
location="/home/michi/src/apache/lenya/trunk/build/lenya/webapp/WEB-INF/lib/cocoon-2.1.8-dev.jar"/> 

  </path>

  <path id="classpath.lenya.xml">
    <pathelement 
location="/home/michi/src/apache/lenya/trunk/build/lenya/webapp/WEB-INF/lib/jing-20030619.jar"/> 

    <pathelement 
location="/home/michi/src/apache/lenya/trunk/build/lenya/webapp/WEB-INF/lib/log4j-1.2.11.jar"/> 

    <pathelement 
location="/home/michi/src/apache/lenya/trunk/build/lenya/webapp/WEB-INF/lib/xml-commons-resolver-1.1.jar"/> 

  </path>

  <path id="classpath.lenya.ac">
    <pathelement 
location="/home/michi/src/apache/lenya/trunk/build/lenya/webapp/WEB-INF/lib/avalon-framework-api-4.1.5.jar"/> 

    <pathelement 
location="/home/michi/src/apache/lenya/trunk/build/lenya/webapp/WEB-INF/lib/avalon-framework-impl-4.1.5.jar"/> 

    <pathelement 
location="/home/michi/src/apache/lenya/trunk/build/lenya/webapp/WEB-INF/lib/cocoon-2.1.8-dev.jar"/> 

    <pathelement 
location="/home/michi/src/apache/lenya/trunk/build/lenya/webapp/WEB-INF/lib/commons-codec-1.3.jar"/> 

    <pathelement 
location="/home/michi/src/apache/lenya/trunk/build/lenya/webapp/WEB-INF/lib/endorsed/jakarta-regexp-1.4.jar"/> 

    <pathelement 
location="/home/michi/src/apache/lenya/trunk/build/lenya/webapp/WEB-INF/lib/excalibur-sourceresolve-1.1.jar"/> 

    <pathelement 
location="/home/michi/src/apache/lenya/trunk/build/lenya/webapp/WEB-INF/lib/jcifs-mock.jar"/> 

    <fileset dir="build/classes/org/apache/lenya/xml">
      <include name="**.class"/>
    </fileset>
    <fileset dir="build/classes/org/apache/lenya/util">
      <include name="**.class"/>
    </fileset>
    <fileset dir="build/classes/org/apache/lenya/net">
      <include name="**.class"/>
    </fileset>
  </path>


There were suggestions that we offer Lenya as a jar, whereas I think we 
should go one step further and offer the various components as jars if 
possible (Access Controller, Workflow, ...) because this would allow to 
re-use Lenya also within other application and not just within Lenya 
itself.

Thanks

Michi


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]