(unfortunately my POP account is holding 360 of my emails hostage. Many of those are to this mailing list sent during J1. Until I get those I will not be able to comment on any message sent during that period. Hence I might be commenting on things you already figured out while I was away. Sorry. Kind of) Regarding where to put what XML information. Currently everything is in jboss.xml and jaws.xml respectively. It has been suggested to put this into separate files. My suggestions is to do both: ContainerConfigurations and Type Mappings should indeed be placed in separate files, and EJX plugins should be created for them. But this is for edit mode only. When an EJB application is to be deployed (using the jBoss XML plugin/JAWS XML plugin) the deployer may choose from the CC's and TM's respectively, and the *chosen ones* will then be embedded in the jboss.xml and jaws.xml files. It should not be possible to edit these from within the jBoss/JAWS plugins. The reason for adding these into jboss.xml and jaws.xml is that a deployment (.jar file) needs to be complete. There may not be any information necessary to deploy it which is not contained within it. The solution suggested here would make it easy to have a global reposity of almost static CC's and TM's, yet the apps will contain all info needed to deploy them. Makes sense? /Rickard -- Rickard �berg @home: +46 13 177937 Email: [EMAIL PROTECTED] http://www.telkel.com http://www.jboss.org http://www.dreambean.com
