I would be happy to discuss what such a service will look like
as long as we have all the interested parties contributing their use cases.
IDE, admin-console, portal, JMX, etc.
This is probably best done a separate thread.
View the original post :
http://www.jboss.org/index.html?module=bb&op=vie
We only touched upon this meta-metadata service during our discussions,
defining the
requirements for integration with the MC and what is currently provided for AOP.
i.e. at the component level
I think it would have been presumptous of us to try to imagine all the use cases
that such a service wo
Another overview I would like to see us work to is an interaction diagram type
of description for an ejb3 type of deployment. The key thing is how various
layers of the micro-container affect the deployment, runtime behavior,
redeployment, and management of the ejb3 component and its associated
So the notion of the metadata service and its relation to the aspects such as
the ClassData, and Annotation pieces does not clearly jump out at me after
reading through the overview links.
Its clear that there is a competing view between the simple development
metadata model that wants to move
