TWIMC,
After reading the documentation online tonight, I have a few things to point out and a few questions:
1) On Avalon Meta Info descriptor page (http://avalon.apache.org/meta/meta/info/type/info.html), what are the default values for various optional parameters such as version (1.0?), lifestyle, and collection. With regards to collection, is there some more information I can reference? I'm not intimately familiar with those garbage collection options (e.g., decommission upon memory contention???)
Have just updated the docs to get some clearer descriptions of the collection semantics and info about default policy (which is "hard" collection semantics). Additional information of reference handling is available under the java.lang.ref package description.
Note that other elements of the meta xml description are not given default values elsewhere...
2) With the repository RI (http://avalon.apache.org/repository/about/reference.html), what is the order of precedence for resolving the location of the avalon.properties file? In general, I find that with Maven, the repository, etc. I'm very confused about location precedence of various configuration files...
The page you have referenced in now a out of date and I'll fix this shortly. Instead of referencing avalon.properties - the behavior is now [app].properties where [app] is the name of an application that is supplied to the repository initial context. For example in Merlin the app name is "merlin" which means that all properties are under the merlin.properties space.
Concerning the property file resolution order - it should be the working directory, the user's home directory, the application directory. Looking at the current docs - none is this very clear so I'm planning on digging into doc and docs and make sure this is properly detailed.
3) Is there an example of a component declaring required permissions using PermissionDescriptor (http://avalon.apache.org/meta/meta/info/type/security/permission.html)? In general, I'm clueless as to what that page is saying. An example of role-based access to a component would be greatly appreciated.
I've just commented out this stuff in the docs in cvs - basically its work in progress.
I've also updated the meta docs earlier today to improve layout and access to key information. The updated docs will probably be on-line tomorrow.
Cheers, Stephen.
Thanks! The docs are getting very good indeed!!
Justin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
