Thank you for the direction, I reviewed the dev-list thread and the new class diagrams. I had a couple more questions...
anonymous wrote : | "This should be introducing overrides/defaults at a layer above the application deployment level." 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. 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"? 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? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3910575#3910575 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3910575 ------------------------------------------------------- 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 JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
