[
https://jira.jboss.org/browse/JBIDE-6483?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick reassigned JBIDE-6483:
----------------------------------------
Assignee: Rob Stryker (was: Brian Fitzpatrick)
Rob, I'm not asking you to fix this, but asking for some input...
If you look at org.jboss.tools.esb.core.runtime.ESBRuntimeResolver_47 (in
org.jboss.tools.esb.project.core), you'll notice that we're blindly defaulting the
server configuration to "default"...
IPath soapDeployPath =
rtHome.append(SOAP_AS_LOCATION).append("server").append("default").append(
"deployers").append("esb.deployer").append("lib");
IPath deployPath =
rtHome.append("server").append("default").append(
"deployers").append("esb.deployer").append("lib");
Obviously this is a bad thing and explains a number of things to me.
So... We need to somehow figure out how to get the server configuration from the server
list and use that instead. Is there an easy way to do this?
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