[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-6483) ESB 4.7 runtime detection depends on default server configuration

[Brian Fitzpatrick (JIRA)]

    [ https://jira.jboss.org/browse/JBIDE-6483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12536101#action_12536101 ] 

Brian Fitzpatrick commented on JBIDE-6483:
------------------------------------------

To clarify what I meant by saying this "explains a number of things to me"...

When you deploy a web service project to a JBoss SOA-P runtime (I'm guessing anything that supports ESB 4.7 at the moment) a part of the deployment places a copy of the WSDL in the [runtime]/server/default/data/wsdl directory as a WAR file.

08:34:26,511 INFO  [DefaultEndpointRegistry] register: jboss.ws:context=MyRSSSearchProject,endpoint=GsearchrssSoap
08:34:26,617 INFO  [TomcatDeployment] deploy, ctxPath=/MyRSSSearchProject
08:34:26,977 INFO  [WSDLFilePublisher] WSDL published to: file:/NotBackedUp/bfitzpat/runtimes/jboss-soa-p.5.0.0/jboss-as/server/default/data/wsdl/MyRSSSearchProject.war/GsearchrssSoap7749654244463029180.wsdl

The code in ESBRuntimeResolver_47 explains why this WSDL is going here. But it doesn't get cleaned up when you remove the project from the server and undeploy it. That's a separate mystery I guess. 

> ESB 4.7 runtime detection depends on default server configuration
> -----------------------------------------------------------------
>
>                 Key: JBIDE-6483
>                 URL: https://jira.jboss.org/browse/JBIDE-6483
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: esb
>    Affects Versions: 3.1.0.GA, 3.1.1
>            Reporter: Martin Putz
>            Assignee: Rob Stryker
>             Fix For: 3.1.x, 3.2.x
>
>
> When attempting to add SOA-P 5 as an ESB runtime to JBDS 3.0.0, this is only possible if a 'default' server configuration exists. If the 'default' server configuration is renamed to something else (like 'development' for example) then the runtime is not valid.
> org.jboss.tools.esb.core.runtime.ESBRuntimeResolver_47#getJarDirectories(..) has a hard-coded reference to the "default" directory.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira