Bill Burke wrote:
XPATHs would be a perfect fit for something like this. Why recreate?Another thing that MBeans don't seem to address is the notion of layered configuration or in other words configuration domains. Each layer can inherit/modify the configuration from a top level layer. Cluster wide config. Per APp server config tailored to each machine. Overrides at the component and invocation level. Let's take a use-case. Let's say I want to change config cluster-wide for one particular attribute. Let's say DB connection pool max size. What you have to do now is go to each and every machine to do this.
Bill to me this XML stuff is just an implementation detail. The important questions are:
* Where does the metadata live? Is it hanging off the container, application or a toplevel domain?
I would assume the container has a ref to a service that maybe shared across the domain, but the container doesn't care as it only has a simple interface.
* How is the data loaded into the repository?
I am thinking of specialized loader classes that in the example of ejb fill the repository with method level metadata like security and tx
* How are changes propagated from the repository to the physical structure and the other way around.
I have no idea on that one.
-dain
-------------------------------------------------------
This sf.net email is sponsored by: Are you worried about your web server security? Click here for a FREE Thawte Apache SSL Guide and answer your Apache SSL security needs: http://www.gothawte.com/rd523.html
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
