[JBoss JIRA] Created: (JBIDE-5108) JBossRuntimeManager has hard-coded the configuration to default
by Rob Stryker (JIRA)
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
16 years, 4 months
[JBoss JIRA] Created: (JBIDE-4864) BPEL Process Versioning
by Brian Fitzpatrick (JIRA)
BPEL Process Versioning
-----------------------
Key: JBIDE-4864
URL: https://jira.jboss.org/jira/browse/JBIDE-4864
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: bpm
Affects Versions: 3.1.0.M4
Reporter: Brian Fitzpatrick
Assignee: Denny Xu
The process versioning requirement is to support an optional 'version' attribute on the top level 'deploy' element in the bpel-deploy.xml deployment descriptor, and
provide:
1) Extension to ODE deployment descriptor editor to allow user to define the version.
2) When BPEL project is deployed to AS server, if a version has been specified, then it should be used as the suffix of the jar name.
The version attribute should be defined in its own namespace - open to suggestions?
--
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
16 years, 4 months