"[EMAIL PROTECTED]" wrote : | What do you mean by 'layer' here? How does this relate to "scope" in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossKernelMetaData? i.e. the "THREAD, REQUEST, SESSION, DEPLOYMENT, APPLICATION, SERVER, CLUSTER, DOMAIN" levels you mention here http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3910490#3910490. | The layer I am talking about is related to the scope only in that the management layer sources metadata at certain layers. The scope just defines an ordering of metadata that will allow a runtime consumer to choose between various priorities of metadata. The management layer would be a source of metadata at the deployment and higher levels since its not typically a runtime notion. However, you could have a management console that introduced runtime changes that should not be persisted that did in fact populate say the session level metadata.
By layer I mean a management aspect that layers on top of the bean deployments which introduces the management concern. Unlike the current jboss4 jmx based kernel, management via an aspect like jmx is not a fundamental notion. Some configuration layer would have to introduce this concern to some subset or all of the beans. Certainly the jboss5 configuration of the mc will introduce a management aspect, including legacy adaptors that allow the jmx mbeans to integrate. "[EMAIL PROTECTED]" wrote : | What's the relationship between the metadata repository and the bean itself? How do the two interact across the beans lifecycle? Will you be able to update a beans metadata by using the metadata repository directly or only through the beans "management interface"? | It really depends on how the deployers/aspects associated with the bean make use of the repository. "[EMAIL PROTECTED]" wrote : | anonymous wrote : | | "It comes into play at the level of the metadata repository + that aspects associated with the path being used to update the state (jmx, some other management interface)." | | Are you saying that the interface used to update a beans metadata could determine whether or not the change is permanent? | | Are there plans to document use cases/sequence diagrams at the 'Microcontainer' level or at the 'AppServer atop the MC' level? | Yes, just as today with the jmx management api, persistence is a configuration detail. As we move into the creation of the management aspects, interaction with the persistent state of the metadata repository and profile service will have to be considered. I do plan on documenting the key usecases and interactions as the mc gets built out. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3910577#3910577 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3910577 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
