There was a big thread "Moving to thread local enc/metadatageneralization" touching on the repository so I would look at that. See the jboss-development list archives.
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossDeveloperChannels a) is really an ambiguous question because its an implementation detail of the deployer processing the descriptor. It could be the same as today where a redeployment occurs, it could "know" that changes only affected attributes and update the metdata or try to pass these to the beans management interface, etc. In short, this behavior is not a fixed design element at this point. b) See some of the class diagrams out here under (Class Diagrams for Evolving JBoss5): http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossKernel Also from this page, one of the main design issues is to have a POJO based model at the lowest level, so fundamentally xml is irrelevant. Its just one supported configuration mechanism. c+d) At the lowest level this notion does not exist. 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). In general the notion of the repository is that the bean metadata can be obtained from a collection of sources at different levels from class annotations, deployment descriptors, serve defaults, admin defaults, etc. Because there is no hard coupling between a bean and its management interface (as is the case with the jmx based mc), this question can't be answered. There will be support for using jmx as the management view of course. Your first big disconnect between the way things are done today(jboss4) vs how jboss5/Microcontainer will behave is that the bundled deployment descriptors should not be viewed as something that is manipulated by the admin/management layer. This should be introducing overrides/defaults at a layer above the application deployment level. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3910479#3910479 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3910479 ------------------------------------------------------- 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
