[ https://jira.jboss.org/jira/browse/JBESB-2177?page=com.atlassian.jira.plu... ] Work on JBESB-2177 started by Kevin Conner. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBESB-2177?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-2177: ------------------------------------- The schema support can now handle two different schemas, the current version (equivalent to the jbossesb-1.0.1 xsd used in the SOA platform 4.4 release) and a new version, jbossesb-1.1.0.xsd, which can be modified. The classes referring to the specific models are now contained within two packages, one handling the mapper layer and its translation with a second handling the model abstractions. These packages are org.jboss.soa.esb.listeners.config.mappers - schema manipulation for jbossesb-1.0.1.xsd org.jboss.soa.esb.listeners.config.mappers110 - schema manipulation for jbossesb-1.1.0.xsd and org.jboss.soa.esb.listeners.config.model - model abstraction and external views I have modified all external references so that they now use the model abstraction rather than the direct xmlbeans model. The mappers for 1.1.0 are a straight copy of the 1.0.1 version but refer to a model generated with the new namespace. This is not an ideal solution but, because of the current schemas and their mapping layer, is the least invasive. We need to be careful going forward that modifications to the listeners/gateways, in support of a new schema, do not break previous versions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira