[JBoss JIRA] Created: (JBIDE-6483) ESB 4.7 runtime detection depends on default server configuration
11:29 a.m.
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.1, 3.1.0.GA
Reporter: Martin Putz
Assignee: Brian Fitzpatrick
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
3:35 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6483) ESB 4.7 runtime detection depends on default server configuration
[
https://jira.jboss.org/browse/JBIDE-6483?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick updated JBIDE-6483:
-------------------------------------
Fix Version/s: 3.1.x
3.2.x
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: Brian Fitzpatrick
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
4:25 p.m.
New subject: [JBoss JIRA] Assigned: (JBIDE-6483) ESB 4.7 runtime detection depends on default server configuration
[
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
5:15 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6483) ESB 4.7 runtime detection depends on default server configuration
[
https://jira.jboss.org/browse/JBIDE-6483?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick commented on JBIDE-6483:
------------------------------------------
To clarify what I meant by saying this "explains a number of things to me"...
When you deploy a web service project to a JBoss SOA-P runtime (I'm guessing anything
that supports ESB 4.7 at the moment) a part of the deployment places a copy of the WSDL in
the [runtime]/server/default/data/wsdl directory as a WAR file.
08:34:26,511 INFO [DefaultEndpointRegistry] register:
jboss.ws:context=MyRSSSearchProject,endpoint=GsearchrssSoap
08:34:26,617 INFO [TomcatDeployment] deploy, ctxPath=/MyRSSSearchProject
08:34:26,977 INFO [WSDLFilePublisher] WSDL published to:
file:/NotBackedUp/bfitzpat/runtimes/jboss-soa-p.5.0.0/jboss-as/server/default/data/wsdl/MyRSSSearchProject.war/GsearchrssSoap7749654244463029180.wsdl
The code in ESBRuntimeResolver_47 explains why this WSDL is going here. But it doesn't
get cleaned up when you remove the project from the server and undeploy it. That's a
separate mystery I guess.
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
10:14 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6483) ESB 4.7 runtime detection depends on default server configuration
[
https://jira.jboss.org/browse/JBIDE-6483?page=com.atlassian.jira.plugin.s...
]
Max Rydahl Andersen commented on JBIDE-6483:
--------------------------------------------
im quite sure this is a very old and duplicated issue.
ESB config should get the default config name from AS when it is a JBoss AS included ESB.
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
10:16 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6483) ESB 4.7 runtime detection depends on default server configuration
[
https://jira.jboss.org/browse/JBIDE-6483?page=com.atlassian.jira.plugin.s...
]
Max Rydahl Andersen updated JBIDE-6483:
---------------------------------------
Priority: Critical (was: Major)
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
Priority: Critical
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
7:23 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6483) ESB 4.7 runtime detection depends on default server configuration
[
https://jira.jboss.org/browse/JBIDE-6483?page=com.atlassian.jira.plugin.s...
]
Rob Stryker commented on JBIDE-6483:
------------------------------------
good catch
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
Priority: Critical
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
7:56 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-6483) ESB 4.7 runtime detection depends on default server configuration
[
https://jira.jboss.org/browse/JBIDE-6483?page=com.atlassian.jira.plugin.s...
]
Rob Stryker resolved JBIDE-6483.
--------------------------------
Fix Version/s: 3.2.0.M1
Resolution: Done
Horrible oversight in the code, thanks for pointing it out.
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
Priority: Critical
Fix For: 3.1.x, 3.2.0.M1, 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
11:06 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6483) ESB 4.7 runtime detection depends on default server configuration
[
https://jira.jboss.org/browse/JBIDE-6483?page=com.atlassian.jira.plugin.s...
]
Rob Stryker updated JBIDE-6483:
-------------------------------
Fix Version/s: 3.1.2
3.2.0.Beta1
(was: 3.2.x)
(was: 3.1.x)
(was: 3.2.0.M1)
jira cleanup
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
Priority: Critical
Fix For: 3.1.2, 3.2.0.Beta1
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
4995
days inactive
5126
days old
jbosstools-issues@lists.jboss.org
8 comments
4 participants
participants (4)
-
Brian Fitzpatrick (JIRA) -
Martin Putz (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Rob Stryker (JIRA)