The idea is to keep it as simple as possible, like the -ds.xml You are supposed to hide the implementation (the target of the metadata) so it can be changed in future without breaking applications. The user doesn't care if a piece of metadata is consumed by the pool, CM, MCF, etc.
I would expect to see a top level metadata object with most values. I think you only need a different metadata object for the properties. So I would suggest: ConnectionFactoryMetaData (the main object) ConnectionFactoryPropertiesMetaData (MCF config) ConnectionPropertyMetaData (getConnection properties for local jdbc) XADataSourcePropertyMetaData (XADataSource properties) DataSourceMetaData would be an alternate main object that specializes ConnectionFactoryMetaData with the magic pixie dust. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3836720#3836720 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3836720 ------------------------------------------------------- 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
