[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-8516) Importing ESB 5 examples, with a mis-named SOA5 runtime does not display the same level or detail of error as if no SOA5 runtime was installed

[Snjezana Peco (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-8516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Snjezana Peco resolved JBIDE-8516.
----------------------------------

    Fix Version/s:     (was: 3.3.x)
       Resolution: Done


> The problem is that if a user installs a SOA5 runtime, but gets the name wrong - then the error message and detail dialog shown in the first screenshot are not displayed.

Project examples in JBDS 4 don't require  the name of  a runtime to be "jboss-soa-p.5.0 Runtime". If there is a SOAP-P 5.x runtime (a runtime of the type "org.jboss.ide.eclipse.as.runtime.eap.50" with the esb component), the project  examples engine will change the name of that runtime to some SOA-P 5.x that exists in the workspace after importing an example. 
You can test it in the following way:

- create a SOAP-5 5.x runtime with the "SOA-P 5.x" name
- import  the "JBoss ESB HelloWorld Example - ESB" example

The project example will be imported without any compile errors. If you right-click the helloworld or helloworld_testclient project, select Properties>Targeted Runtimes, you will see that the "SOA-5 5.x" runtime is checked.

If you try the same test case using the "JBoss ESB HelloWorld Action Example - ESB", you will get compile errors in the helloworld_action_client" project. The problem happens because this example doesn't have the correct fix. The fix looks as follows:

<fix type="wtpruntime">
	<property name="allowed-types">org.jboss.ide.eclipse.as.runtime.eap.50</property>
	<property name="eclipse-projects">helloworld_action</property>
	<property name="required-components">esb</property>
	<property name="description">This project example requires the JBoss SOA-P 5.0 and the runtime name should be "jboss-soa-p.5.0 Runtime"</property>
</fix>

The eclipse_projects property contains a list of Eclipse projects that need to be fixed. 
This fix requires the helloworld_action project to contain the SOAP-5 runtime, but helloworld_action_client doesn't have to have that requirement. 
When importing the project example, you will see that the target runtime for the helloworld_action project is correct, but is not for the the helloworld_action_client project .

The correct fix:

<fix type="wtpruntime">
	<property name="allowed-types">org.jboss.ide.eclipse.as.runtime.eap.50</property>
	<property name="eclipse-projects">helloworld_action, helloworld_action_client</property>
	<property name="required-components">esb</property>
	<property name="description">This project example requires the JBoss SOA-P 5.x"</property>
</fix>

The same problem is in the remaining ESB for SOA-P 5 examples.
I have fixed all those project examples. The fix is avaliable in JBDS 4.0.1 (the JBoss Developer Studio 4 site). 


> Importing ESB 5 examples, with a mis-named SOA5 runtime does not display the same level or detail of error as if no SOA5 runtime was installed
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-8516
>                 URL: https://issues.jboss.org/browse/JBIDE-8516
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: esb, project-examples
>    Affects Versions: 3.2.0.CR1
>         Environment: Version: 4.0.0.GA Build id: v20110216-1930-H239-GA Build date: 20110216-1930
> SOA-P 5.1 GA
> JBoss Tools
>    http://download.jboss.org/jbosstools/updates/nightly/trunk/ (BPEL editor)
>     1.0.0.v20110217-0324-H60-Alpha1 
>            Reporter: Len DiMaggio
>            Assignee: Snjezana Peco
>             Fix For: 3.2.1
>
>         Attachments: Screenshot-1.png, Screenshot-2.png
>
>


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira