Stefano Maestri [http://community.jboss.org/people/maeste] replied to the discussion "JCA / Datasources in domain.xml" To view the discussion, visit: http://community.jboss.org/message/557508#557508 -------------------------------------------------------------- Hi all, I've discussed a bit about this point with  Alexey Loubyansky on IRC channel. I was asking some feedback about the posted xsd. I'm trying to write down the main contents of our discussion here to keep others post and then I'll try to resume our conclusion about how many xsd we need to have JCA stuffs included in domain.xml and also usable for standalone version of IronJacamar project. Please note here we are referring to a standalone JCA implementation and not standalone configuration of As for which we don't need anything different than domain.xml from a JCA config point of view. Of course if I've missed and/or misunderstood something, Alexey please precise that points. *Feedback* The main points Alexey had about the xsd is: * Name conventions (also David had pointed me out on this point). *STATUS ON THIS POINT*: I've already fixed type names in last committed version of xsd. I've tried to follow what I can see for example in /jboss-as-domain/src/main/resources/schema/jboss-domain-mod_cluster.xsd. Anyway have a look to the last committed xsd and let me know if something still missed/wrong. * namespace: I need to define the namespace used for jca definition. Conventional namespace name is "urn:jboss:domain:whateveryouwant:1.0". *STATUS ON THIS POINT*: the namespace will be set in the top level xsd (let me call it jca.xsd) which will include other xsd (see conclusion) * Number of xsd. I've explained I was planning to have different xsds for datasources (the committed one) and for connection-factories. Alexey thinks it's better to have just one xsd with multiple top-level element possible to limit the number of xsd, and much more important limit the number of namespaces. *STATUS ON THIS POINT*: see the next feedback and the conclusion. We agreed about an xs:include based solution giving multiple xsds file included in jca.xsd file with only one namespace used into the AS domain.xml * I've explained to Alexey that IronJacamar (JCA project) needs these xsds too while it doesn't need a top level jca root tag with globla configuration. As Jesper explained in a previous post AS7 jca stuffs need some global configuartions (ArchiveValidation, ArchiveValidationFailOnWarn etc) exposing some of the attributes that IronJacamar currently have on its  deployer in order for users to setup their BootstrapContext's.  *STATUS ON THIS POINT:* see conclusions. *Conclusions* * We need at least 3 xsd: jca.xsd for AS7 and an xsd for ironJacamar stanalone. The first one will define  urn:jboss:domain:jca:1.0 namespace, tags for global configs and will include datasources and connectionfactories xsds (one containing both or 2 xsd at this level isn't a big difference). The second one just define a root tag, with its own namespace and will include DS and CF stuffs. The best solution we see (at xsd level) is to define DS and CF xsds without namesapce and then use in the 2 top level xsd (AS and JCAStandalone) xs:include directive to include all definition there. These solution should permit us to have in fact common definitions defined in DS&CF xsd (or 2 xsds as said, since using include it's just matter of number of files and not namespaces), and specific definitions in jca's AS xsd and ironJacamar standalone one. These is an advantage because we could have different life cycle for different configuaration levels, permitting in particular to add something at AS or standalone top level configs without impact each other. Any comments are more than welcome regards S. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/557508#557508] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]