[jbosstools-issues] [JBoss JIRA] (JBDS-2447) Issues to be resolved in SOA 5.0.3 Tooling

[ https://issues.jboss.org/browse/JBDS-2447?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-2447: ------------------------------------ Len discovered this issue: "I have multiple runtimes installed. I create a new project and reference the SOA 5.2 (aka esb 4.10) runtime - and the project creation dialog/wizard tells me I have 4.12 " My response: The issue you've discovered really isn't a new one, but I have a better understanding of what's going on... So let me try to explain. For each version of ESB, we have declared an explicit facet. In org.jboss.tools.esb.project.core, we have facets defined (4.2,4.3,4.4,4.5,4.6,4.7,4.9,4.10,4.11,4.12) and assign them to EAP runtime components (4.3,5.0,6.0) (which are specified in the AS tools plug-ins). The "New ESB Project" wizard extends org.eclipse.wst.web.ui.internal.wizards.NewProjectDataModelFacetWizard and the first page extends org.eclipse.wst.web.ui.internal.wizards.DataModelFacetCreationWizardPage. We don't do any customizing to that page beyond telling it which facets (i.e. ESB) we want to use for the new project. (The fact that these are internal classes doesn't help.) The first page is the one that gathers the runtimes (Target Runtime drop-down) and the facet versions (JBoss ESB Version drop-down). If I select a pre-defined runtime (let's say JBoss SOA-P 5.2 GA, which shipped with ESB 4.10), because of the way we have facets defined and associated with EAP runtimes, it automatically selects ESB version 4.12, because it's the highest supported ESB facet version associated with an EAP 5.x runtime. It does this by default. So at this point, the user has to know what version of ESB they are working with and change the version drop-down accordingly. This selection in turn selects the "ESB Config Version" on the "Install ESB Facet" page later in the project wizard. If they leave the ESB version alone, the config version defaults to 1.3.1, which should work for ESB 4.11/4.12 but may cause issues going against ESB 4.10 which expects config version 1.3.0. (Len tested deploying an empty ESB project configured for 4.12 to SOA-P 5.2/ESB 4.10 and it seems to have worked, but will do more testing on this I'm sure). Ultimately there's a usability nightmare in this particular combination of pages and settings that we'll need to address eventually. That said, this particular issue has been around as far back as I can see in the code. Max says: "I suggest putting this issue in jira with this excellent write up and look for a solution in the next feature release of esb/soa tools - not something we should try fix in JBT 3.3.x/JBDS 5.x stream." Follow up questions from Len: "On this question: 'If they leave the ESB version alone, the config version defaults to 1.3.1, which should work for ESB 4.11/4.12 but may cause issues going against ESB 4.10 which expects config version 1.3.0.' I haven't yet been able to create a problem with this - but I *think* users can run into trouble if they attempt to use a feature that was introduced in 1.3.1, but thy have specified 1.3.0 - But - they can always modify the schema setting." -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira