10:24 p.m.
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
8:27 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5108) JBossRuntimeManager has hard-coded the configuration to default
[
https://jira.jboss.org/jira/browse/JBIDE-5108?page=com.atlassian.jira.plu...
]
Denny Xu commented on JBIDE-5108:
---------------------------------
Basically, the JBossRuntimeManager doesn't care about what the configuration is, the
only thing it does is to get ESB runtime jars from a given location,
the location may be a standalone ESB runtime, SOA-P , EAP and also can be a location of
JBossAS with ESB runtime get installed, what does JBossRuntimeManager do is to get the
locations of "jbossesb.esb" and "jbossesb.sar" and then pick up jars
from the locations and add jars to the
project ClassPath, it doesn't depend on the any Server IRuntime object and it should
require have to configure a JBoss Server Runtime at the beginning,
in other worlds, one ESB runtime doesn't mean there should be a corresponding JBoss
Server Runtime.
The only issue is that if the user use community JBoss AS and get ESB runtime installed to
non-default configuration, it would not get the esb runtime
location, so maybe scan all available configurations is a good choice.
"Also the same class has the following if statement twice: "
the two statement is not the same, the first one means if the esbPath is not exist then
try to consider the location is a ESB standalone location,
the second one means if the location is not a standalone ESB then treat it as a SOAP
location.
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
10:26 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-5108) JBossRuntimeManager has hard-coded the configuration to default
[
https://jira.jboss.org/jira/browse/JBIDE-5108?page=com.atlassian.jira.plu...
]
Denny Xu updated JBIDE-5108:
----------------------------
Fix Version/s: LATER
(was: 3.1.0.CR1)
Priority: Minor (was: Critical)
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: Minor
Fix For: LATER
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
12:47 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-5108) JBossRuntimeManager has hard-coded the configuration to default
[
https://jira.jboss.org/jira/browse/JBIDE-5108?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-5108:
---------------------------------------
Fix Version/s: 3.1.0.CR1
(was: LATER)
Priority: Critical (was: Minor)
this just sounds so very wrong.
If the user is using an AS server/runtime with ESB in it then of course it needs to pick
up these jars from the proper configuration. Taken a hardcoded one is not acceptable since
as you say you self - the location is not the same always.
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
12:49 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5108) JBossRuntimeManager has hard-coded the configuration to default
[
https://jira.jboss.org/jira/browse/JBIDE-5108?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-5108:
--------------------------------------------
note, i'm marking it cricial for CR so we at least can have the discussion on what
should actually happen!
i.e. why doesn't we use AS adapter for standalone ESB runtimes ? (isn't that just
a reduced AS anyway ?)
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
9:38 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5108) JBossRuntimeManager has hard-coded the configuration to default
[
https://jira.jboss.org/jira/browse/JBIDE-5108?page=com.atlassian.jira.plu...
]
Denny Xu commented on JBIDE-5108:
---------------------------------
In current JBoss ESB runtime definition framework, require the user specify a location
where the ESB runtime installed, the location can point to the following three types of
ESB runtime distribution:
1. JBoss ESB standalone distribution, if the user use this type of ESB runtime, ESB tools
will pick up jars from directories : /jbossesb-4.6/lib/jbossesb.sar/lib and
/jbossesb-4.6/lib/jbossesb.esb,
2. jbossesb-server binary distribution, a pre-configured profile based on the JBoss
Microkernel architecture, if use this type of ESB runtime, pickup jars
from the directories: /jbossesb-server-4.6/server/default/deploy/jbossesb.sar/lib/ and
/jbossesb-server-4.6/server/default/deploy/jbossesb.sar/lib/
3. Community JBoss AS + ESB standalone distribution, pick up jars from
/jboss-4.2.GA/server/*configuration*/deploy/....
the first two location for picking up jars is invariable, only in the 3rd source ESB
runtime , the *configuration* is variable. In esb project wizard, the esb
runtime definition doesn't tie to jboss AS adapter, so it's impossible to get
*configuration* from JBoss AS runtime for now, current ESB runtime definition
is similar to Seam runtime configuration
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
12:31 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5108) JBossRuntimeManager has hard-coded the configuration to default
[
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
12:31 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-5108) JBossRuntimeManager has hard-coded the configuration to default
[
https://jira.jboss.org/jira/browse/JBIDE-5108?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-5108:
---------------------------------------
Priority: Blocker (was: Critical)
Marking as blocker since we need to get this cleaned up.
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: Blocker
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
11 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-5108) JBossRuntimeManager has hard-coded the configuration to default
[
https://jira.jboss.org/jira/browse/JBIDE-5108?page=com.atlassian.jira.plu...
]
Denny Xu updated JBIDE-5108:
----------------------------
Attachment: newesbruntime.gif
the issue fixed, there are some changes below:
for user defined esb runtime from perference page, on this page, I added a *configuration*
field, if the user point the home location to a Jboss AS or SOA-p, there configuration
combo will list all available configurations, if the user select a standalone esb runtime
location, the configuration combo will be empty and the user should ignore the field.
so that the ESB classpath container can pick up jars from specify server configuration or
standalone esb runtime
when the user create ESB project wizard with a server supplied ESB runtime, ESB runtime
classpath container will get configuration from the selected server runtime and then pick
up jars accordingly.
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: Blocker
Fix For: 3.1.0.CR1
Attachments: newesbruntime.gif
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
7:13 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-5108) JBossRuntimeManager has hard-coded the configuration to default
[
https://jira.jboss.org/jira/browse/JBIDE-5108?page=com.atlassian.jira.plu...
]
Denny Xu resolved JBIDE-5108.
-----------------------------
Resolution: Done
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: Blocker
Fix For: 3.1.0.CR1
Attachments: newesbruntime.gif
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
5317
days inactive
5358
days old
jbosstools-issues@lists.jboss.org
9 comments
3 participants
participants (3)
-
Denny Xu (JIRA) -
Max Rydahl Andersen (JIRA)
-
Rob Stryker (JIRA)