[adrian.brock]

"wolfc" wrote:
As for the order: at one point we must have a full set of meta data attached for use in the SecurityDeployer & WebServices.
Either we do parse & scan = complete or scan & parse = complete. Since xml overrides annotations my vote is for: scan then parse.

Actually, xml overrides annotations because they are different things! :-)

Class level metadata == annotations
Instance level metadata == xml (or predetermined attachments)

Instance (the Object level) overrides Class (shared across objects).
The order of populating does not matter if you get this basic fact correct.

See the hierarchical metadata stuff in the jboss-container project
which is also available in aop. This is how we allow instance level annotation
overrides in the microcontainer.

[wolfc]

It's not really as such in EJB 3. We got instance level annotations. It took me a while to realize this. We instantiate a class container per ejb and add annotations to it. Then at the next stage we don't get the annotations from the class, but resolve the annotations from class container.
This works as long as it only affects the ejb bean class. It doesn't work for interceptor classes. So either I've to abandon this model or add extra annotations for instance metadata related to other classes.

[adrian.brock]

You should be able to do instance overrides to any class.
Fundamentally, these need to be coming from the profile service.