Re: persistence configuration errors?

Gene,

What's the problem:
The way it works....Keel's config merge process is looking for all 
pieces of config. that start with <schema id="component-security" 
[.....]> and merges it all together.  At the end of the merge, the 
"schema" element will end up with not just the "id" attribute, but the 
superset of all the attributes provided by all snippets of <schema 
id="component-security" ... >  spread through multiple files.

system.xconf in svc-persist-base only provides "id=...".  
Component-security-persist.xconf in svc-authorization-persist provides 
"id=" as well as "name=".  So in theory, if you look in merged.config, 
you should see "<schema id="component-security" 
name="component-security"> .  Somehow, in your case that did not happen, 
and the container did not find the name= attribute.

Why:
Heck if I know!  Could be because svc-authorization-persist didn't get 
included, maybe? Or, somehow the build process failed mid-stream and 
skipped the svc-authorization-persist?  Look in merged.config just to 
make sure you didn't get multiple <schema id="component-security"> 
definitions by any chance.

Do an ant clean again, and watch carefully for Out Of Memory errors, if 
it happens make sure you set ANT_OPTS env variable to use more memory. 
If this turns out to be OK after that,  (from your /usr/local path, I am 
assuming you are not on WinDOZE, and I have only seen the problem on 
Windows), then I think we should seriously consider taking out the Ant 
"parallel" construct out, it's caused more problems than it is worth.

Shash

Gene McCullough wrote:

>Someone please help me keep my sanity!  I started getting an error after
>deleting my webapp dir and doing an ant clean on my project.
>
>After starting the container, and accessing just the main static page, i
>get this in the system.log file:
>ERROR   2004-04-12 14:13:47.047   [system.command]
>(/org.apache.avalon.fortress.util.FortressCommandFailureHandler.handleCommandFailure(FortressCommandFailureHandler.java:57)): Could not prepare ComponentHandler for: org.keel.services.persist.defaultpersist.DefaultPersistentFactory
>org.apache.avalon.framework.configuration.ConfigurationException: No
>attribute named "name" is associated with the configuration element
>"schema" at Merged [layer:
>file:/usr/local/src/jakarta-tomcat-5.0.19/webapps/occa/WEB-INF/keel/server/conf/svc-persist-base/system.xconf:17:45, base: file:/usr/local/src/jakarta-tomcat-5.0.19/webapps/occa/WEB-INF/keel/server/conf/svc-persist-default/system.xconf:58:45]
>        at
>org.apache.avalon.framework.configuration.DefaultConfiguration.getAttribute(DefaultConfiguration.java:279)
>
>which corresponds to this line in the conf files:
><schema id="component-security">
>
>which eventually results in this at the client:
>            null, null, Unable to provide implementation for
>        org.keel.services.authentication.AuthenticationManager/*
>    (Key='org.keel.services.authentication.AuthenticationManager/*')
>
>I can not find any errors in my build output, nor in any other log
>files, tomcat or keel/server.
>
>this comes after a fresh checkout of cvs early last week.  I can't
>imagine this is enough information for anyone to figure what the heck is
>going on, but I don't know what else to include, and am at my wits end
>(it didn't take long either!)
>
>thanks in advance
>gene
>
>_______________________________________________
>User mailing list
>[email protected]
>http://lists.keelframework.org/listinfo.cgi/user-keelframework.org
>  
>