[
https://jira.jboss.org/jira/browse/JBIDE-5108?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-5108:
--------------------------------------------
How is point 3 different from 1 and 2 if it doesnt use any info from the AS server ?
How is this setup for SOA-P the product that has it all included ? Does the installation
of JBDS configure this so it works out of the box ?
Seam runtimes are different because they are *not* tied to a specific configuration of AS
- the ESB is.
JBossRuntimeManager has hard-coded the configuration to default
---------------------------------------------------------------
Key: JBIDE-5108
URL:
https://jira.jboss.org/jira/browse/JBIDE-5108
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.1.0.M3
Reporter: Rob Stryker
Assignee: Denny Xu
Priority: Critical
Fix For: 3.1.0.CR1
The class has the following code:
IPath soapDeployPath =
rtHome.append(SOAP_AS_LOCATION).append("server").append("default").append("deploy");
IPath deployPath =
rtHome.append("server").append("default").append("deploy");
These are incorrect if the runtime configuration is not default or if some other
preferences have been set to change the location. You should instead adapt the IRuntime
into a IJBossServerRuntime (if possible) and then call
getConfigurationFullPath().append(IJBossRuntimeResourceConstants.DEPLOY);
Also the same class has the following if statement twice:
if (!esbPath.toFile().exists() || !sarPath.toFile().exists()) {
esbPath = libPath.append(JBOSSESB_ESB);
sarPath = libPath.append(JBOSSESB_SAR);
}
if (!esbPath.toFile().exists() || !sarPath.toFile().exists()) {
esbPath = soapDeployPath.append(JBOSSESB_ESB);
sarPath = soapDeployPath.append(JBOSSESB_SAR);
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira