[jboss-dev-forums] [Design of EJB 3.0] - Re:

[bstansberry@jboss.com]

Looking at the current usage in ejb3-interceptors-aop.xml I don't see anything that looks like changing the value of the attribute of an existing annotation; just the addition of annotations if they are missing.  There may be some secret sauce in jboss-aop to do this, although I doubt it. Even if there is, I gotta imagine the xml to specify it would be really complex/breakable.

"scott.stark at jboss.org" wrote : Falling back to hard-coded defaults seems ok, but the code that is setting up the proxy factory should be also getting the full configuration setup based on a container default configuration. I'd rather move away from the injected default annotations to a complete pojo metadata model where the "Stateless Bean" aop domain has a complete specification.
  | 

Yes, the way EJB2 metadata is merged from standardjboss.xml, jboss.xml container-configuration and the bean declaration itself is nice. Obviously EJB3 has different requirements with the use of annotations and nothing like standardjboss.xml.

I'll leave the hard-coded defaults; my concern was less with having those than with launching a discussion on having an external way to change the default.

"scott.stark at jboss.org" wrote : The only thing I can see to do here is to change the default to something like DefaultClusteredCache and expect that the factory bean is configured to alias this correctly. 

Perhaps "DefaultCache".  Al points out this attribute could be consumed by a non-clustered cache as well.  A value like that seems better than "" since if we ever wanted to externalize the aliasing its easier to map in xml.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106157#4106157

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4106157