[jbosstools-issues] [JBoss JIRA] (JBDS-2448) New ESB wizard - version mismatch errors - and a warning message that is not erased

[Brian Fitzpatrick (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750062#comment-12750062 ] 

Brian Fitzpatrick commented on JBDS-2448:
-----------------------------------------

Figured out *what* is going on, but I'm still scratching my head as to why it was designed this way by Denny way back when.

When the user selects an ESB version, it validates it against the runtime specified at the path you provide. In the SOA-P 5.2 case, at least in my local version, it has ESB 4.10 installed. That's the highest version that it will support. So when you change it to 4.11, it freaks out because 4.11 is not supported in the runtime (the right combination of jars is not there) and it starts at 4.2 and works its way up until it finds a version that *IS* supported - which happens to be 4.7. 

This kind of automated "thinking for the user" will only get us in trouble. And I'm hoping that the user leaves the version be for the majority of cases. 

So what I propose is getting rid of the auto-selection dance and pop up an error saying something like "ESB Version X.Y is not supported by the specified runtime." and prevent them from saving it as a new runtime until they correct it. 

I could probably munge the auto-select to be a bit smarter and reset to the highest supported version, but that doesn't tell the user anything. 
                
> New ESB wizard - version mismatch errors - and a warning message that is not erased
> -----------------------------------------------------------------------------------
>
>                 Key: JBDS-2448
>                 URL: https://issues.jboss.org/browse/JBDS-2448
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: SOA Tooling / Platform 
>    Affects Versions: 5.0.3.GA-SOA
>         Environment: Version: 5.0.2.GA
> Build id: v20130119-0035-H249-GA
> Build date: 20130119-0035
> md5sum esb.site.zip 
> 4c149c52a6058edabe0ad84747443877  esb.site.zip
>            Reporter: Len DiMaggio
>            Assignee: Brian Fitzpatrick
>             Fix For: 5.0.3.GA-SOA
>
>
> Steps:
> 1) Create new ESB runtime, select the SOA Platform dir path
> 2) Accept default version, specify a name for the new run-time
> 3) Then - before saving the new ESB runtime change the version number - the results are:
> With an SOA-P 5.2 server (ESB 4.10):
> * The default ESB version displayed is 4.10
> * If this is changed to 4.11, this warning is displayed:
>     No exact match found for ESB runtime version 4.10. Assuming compatible with latest version: 4.7.
> * If the version is changed back to 4.10, the error is still displayed in the wizard
> With an SOA-P 5.3 server (ESB 4.11):
> * The default ESB version displayed is 4.11
> * If this is changed to 4.12, this warning is displayed:
>     No exact match found for ESB runtime version 4.11. Assuming compatible with latest version: 4.12.
> * If the version is changed back to 4.11, the error is still displayed in the wizard
> With an SOA-P 5.3.1.ER3 server (ESB 4.11.1):
> * The default ESB version displayed is 4.11
> * If this is changed to 4.12, this warning is displayed:
>     No exact match found for ESB runtime version 4.11. Assuming compatible with latest version: 4.12.
> * If the version is changed back to 4.11, the error is still displayed in the wizard
> With an SOA-P 5.3.1.ER4 server (edited VERSION file in rosetta.jar to be ESB 4.12):
> * The default ESB version displayed is 4.12
> * If this is changed to 4.11, this warning is displayed:
>     No exact match found for ESB runtime version 4.12. Assuming compatible with latest version: 4.11.
> * If the version is changed back to 4.12, the error is still displayed in the wizard

--
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