After reading the EJB3.0 specification it has become clear to me that Annotations are a perfect abstraction for our configuration meta model. Therefore all new container configurations will be defined in Annotations.
There are a lot of advantages with this approach: 1) It is very easy to express anything and parse anything in XML format as we have an easy mapping from XML to the meta model 2) We are not limited to XML as the configuration format. ANother idea I have is to define container configurations as Java classes with annotations sprinkled in. 3) EJB3 is all about removing deployment descriptors. A configuration model expressed as annotations can be embedded in Bean class files like regular EJB annotations are. Bill View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3835731#3835731 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3835731 ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
