[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5108) JBossRuntimeManager has hard-coded the configuration to default

[Denny Xu (JIRA)]

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

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