problems with default build

Hi all -  hope someone can help.

I was successful building the default project using plug-in 1.2.9 but am 
now having problems building the default project using version  1.2.12.

The following outlines the steps I've taken and the outcomes / system 
responses.
Perhaps someone can see where I've gone wrong? (my apologies for the novel)

Started with clean system
    - deleted existing plug-in from maven plug-in directory
    - deleted the keel-build directory (including repository)
    - >maven clean

 >maven -DartifactId=maven-keel-plugin -DgroupId=keel -Dversion=1.2.12 
plugin:download
    - the plug-in was downloaded - along with several jars as per normal
    - directory structure was created and populated in keel-build
    - build successful

copied files in keel-build/example-projects/default to newly created 
directory /keel_default
 >cd /keel_default
 >maven keel:install
    - required jars were downloaded to repository
    - project.xml was changed - original changed to project.bak
    - build successful

 >maven war
    - more jars were downloaded
    - directory structure was created and populated
    - multiple warnings of duplicates (no errors)
    - build successful

deployed the resultant default.war into tomcat
 >http://localhost:8080/default/
    - the keel welcome screen is displayed
 >http://localhost:8080/default/model.do?model=createdb
    - results in exception report
    - root cause =
        org.keel.services.model.ModelException: [KeelStarter] :Channel 
timed out waiting for response
       
       
keelserver.log reports -
    org.apache.avalon.fortress.InitializationException: Cannot set up 
Container. Startup lifecycle failure
    at 
org.apache.avalon.fortress.impl.DefaultContainerManager.createContainer(DefaultContainerManager.java:182)
    at 
org.apache.avalon.fortress.impl.DefaultContainerManager.initializeContainer(DefaultContainerManager.java:119)
    at 
org.apache.avalon.fortress.impl.DefaultContainerManager.initialize(DefaultContainerManager.java:112)
    at 
org.keel.core.container.KeelContainerFactory.getContainerManager(KeelContainerFactory.java:231)
    at 
org.keel.core.container.KeelContainerFactory.createContainer(KeelContainerFactory.java:624)
    at 
org.keel.core.container.KeelContainerFactory.createContainer(KeelContainerFactory.java:607)
    at 
org.keel.servers.KeelAbstractServer.initialize(KeelAbstractServer.java:132)
    at 
org.keel.servers.KeelAbstractServer.getContainer(KeelAbstractServer.java:112)
    at 
org.keel.servers.direct.KeelDirectServer.run(KeelDirectServer.java:61)
Caused by: 
org.apache.avalon.framework.configuration.ConfigurationException: No 
class found matching configuration name [name: des, location: null:7:38]
    at 
org.apache.avalon.fortress.impl.DefaultContainer.getClassname(DefaultContainer.java:174)
    at 
org.apache.avalon.fortress.impl.DefaultContainer.configure(DefaultContainer.java:108)
    at 
org.keel.core.container.KeelContainer.configure(KeelContainer.java:196)
    at 
org.apache.avalon.framework.container.ContainerUtil.configure(ContainerUtil.java:240)
    at 
org.apache.avalon.fortress.impl.DefaultContainerManager.createContainer(DefaultContainerManager.java:167)
    ... 8 more

the web.xml file includes the lines ...
  <context-param>
       <param-name>keel.config.dir</param-name>
       <param-value>WEB-INF/keel/server/conf</param-value>
  </context-param>

however the directory WEB-INF/keel/server/ does not exist (WEB-INF/keel/ 
does not exist)


Is this something I've done wrong or is there something wrong elsewhere?
 
       ------------------------

I've also noticed there is no project.xml in the nojms-cocoon example 
project (and no clnt-cocoon.jar in the maven/keel/jars dir).
Is it still possible to use cocoon as a front end as I was quite 
impressed with the simplicity of using keel with cocoon?

thanks ,

Warren
http://keelframework.org/documentation.shtml
Keelgroup mailing list
[email protected]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com