[JBoss JIRA] (JBIDE-11267) Remote Configuration, Runtime Server config missing field "Remote Configuration"
7:13 a.m.
Leo Breuss created JBIDE-11267:
----------------------------------
Summary: Remote Configuration, Runtime Server config missing field
"Remote Configuration"
Key: JBIDE-11267
URL: https://issues.jboss.org/browse/JBIDE-11267
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central, JBossAS/Servers
Affects Versions: 3.3.0.Beta2
Reporter: Leo Breuss
Assignee: Snjezana Peco
In the JBoss Runtime Server configuration, I am no longer able to specify the Remote
Configuration (e.g. standalong-full.xml). It seems like this field has been dropped
between 20111208 and today's 3.3.0b2.
In earlier versions, obviously designed for JBoss 6 and earlier, the implementation of the
JBoss Runtime Server for JBoss 7 had some problems. I'm listing here some of the
problems disucussed in the Forum Reference.
1. The path on the server to look for the existence of the configuration was the
concatenation of <Remote Server Home> + "/server/" + <Remote Server
Configuration>. But JBoss 7 has a different layout structure. No /server/ directory.
Interestingly enough, the field Remote Server Home can be set by browsing the remote file
system.
2. In the field "Remote Configuration" you should be able to select the
appropriate configuration file from the remote server file system. Instead, one could
browse for a local configuration, but had to manually strip the absolute path. Only the
filename may remain, because of the concatenation. And the local JBoss installation has to
reflect the remote JBoss regarding the configuration file names. The default value
"default" did not work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:15 a.m.
[
https://issues.jboss.org/browse/JBIDE-11267?page=com.atlassian.jira.plugi...
]
Leo Breuss updated JBIDE-11267:
-------------------------------
Description:
In the JBoss Runtime Server configuration, I am no longer able to specify the Remote
Configuration (e.g. standalong-full.xml). It seems like this field has been dropped
between 20111208 and today's 3.3.0b2.
In earlier versions, obviously designed for JBoss 6 and earlier, the implementation of the
JBoss Runtime Server for JBoss 7 had some problems. I'm listing here some of the
problems disucussed in the Forum Reference.
1. The path on the server to look for the existence of the configuration was the
concatenation of <Remote Server Home> + "/server/" + <Remote Server
Configuration>. But JBoss 7 has a different layout structure. No /server/ directory.
2. In the field "Remote Configuration" you should be able to select the
appropriate configuration file from the remote server file system. (Interestingly enough,
the field Remote Server Home can be set by browsing the remote file system.) Instead, one
could browse for a local configuration file, but had to manually strip the absolute path.
Only the filename may remain, because of the concatenation. And the local JBoss
installation has to reflect the remote JBoss regarding the configuration file names. The
default value "default" did not work.
was:
In the JBoss Runtime Server configuration, I am no longer able to specify the Remote
Configuration (e.g. standalong-full.xml). It seems like this field has been dropped
between 20111208 and today's 3.3.0b2.
In earlier versions, obviously designed for JBoss 6 and earlier, the implementation of the
JBoss Runtime Server for JBoss 7 had some problems. I'm listing here some of the
problems disucussed in the Forum Reference.
1. The path on the server to look for the existence of the configuration was the
concatenation of <Remote Server Home> + "/server/" + <Remote Server
Configuration>. But JBoss 7 has a different layout structure. No /server/ directory.
Interestingly enough, the field Remote Server Home can be set by browsing the remote file
system.
2. In the field "Remote Configuration" you should be able to select the
appropriate configuration file from the remote server file system. Instead, one could
browse for a local configuration, but had to manually strip the absolute path. Only the
filename may remain, because of the concatenation. And the local JBoss installation has to
reflect the remote JBoss regarding the configuration file names. The default value
"default" did not work.
Forum Reference: https://community.jboss.org/message/722946 (was:
https://community.jboss.org/message/722946)
Remote Configuration, Runtime Server config missing field
"Remote Configuration"
--------------------------------------------------------------------------------
Key: JBIDE-11267
URL: https://issues.jboss.org/browse/JBIDE-11267
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central, JBossAS/Servers
Affects Versions: 3.3.0.Beta2
Reporter: Leo Breuss
Assignee: Snjezana Peco
Labels: RSE, runtime
In the JBoss Runtime Server configuration, I am no longer able to specify the Remote
Configuration (e.g. standalong-full.xml). It seems like this field has been dropped
between 20111208 and today's 3.3.0b2.
In earlier versions, obviously designed for JBoss 6 and earlier, the implementation of
the JBoss Runtime Server for JBoss 7 had some problems. I'm listing here some of the
problems disucussed in the Forum Reference.
1. The path on the server to look for the existence of the configuration was the
concatenation of <Remote Server Home> + "/server/" + <Remote Server
Configuration>. But JBoss 7 has a different layout structure. No /server/ directory.
2. In the field "Remote Configuration" you should be able to select the
appropriate configuration file from the remote server file system. (Interestingly enough,
the field Remote Server Home can be set by browsing the remote file system.) Instead, one
could browse for a local configuration file, but had to manually strip the absolute path.
Only the filename may remain, because of the concatenation. And the local JBoss
installation has to reflect the remote JBoss regarding the configuration file names. The
default value "default" did not work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:38 a.m.
[
https://issues.jboss.org/browse/JBIDE-11267?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-11267:
----------------------------------------
Fix Version/s: 3.3.0.Beta3
Affects Version/s: (was: 3.3.0.Beta3)
Forum Reference: https://community.jboss.org/message/722946 (was:
https://community.jboss.org/message/722946)
Remote Configuration, Runtime Server config missing field
"Remote Configuration"
--------------------------------------------------------------------------------
Key: JBIDE-11267
URL: https://issues.jboss.org/browse/JBIDE-11267
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central, JBossAS/Servers
Reporter: Leo Breuss
Assignee: Snjezana Peco
Labels: RSE, runtime
Fix For: 3.3.0.Beta3
In the JBoss Runtime Server configuration, I am no longer able to specify the Remote
Configuration (e.g. standalong-full.xml). It seems like this field has been dropped
between 20111208 and today's 3.3.0b2.
In earlier versions, obviously designed for JBoss 6 and earlier, the implementation of
the JBoss Runtime Server for JBoss 7 had some problems. I'm listing here some of the
problems disucussed in the Forum Reference.
1. The path on the server to look for the existence of the configuration was the
concatenation of <Remote Server Home> + "/server/" + <Remote Server
Configuration>. But JBoss 7 has a different layout structure. No /server/ directory.
2. In the field "Remote Configuration" you should be able to select the
appropriate configuration file from the remote server file system. (Interestingly enough,
the field Remote Server Home can be set by browsing the remote file system.) Instead, one
could browse for a local configuration file, but had to manually strip the absolute path.
Only the filename may remain, because of the concatenation. And the local JBoss
installation has to reflect the remote JBoss regarding the configuration file names. The
default value "default" did not work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:17 a.m.
[
https://issues.jboss.org/browse/JBIDE-11267?page=com.atlassian.jira.plugi...
]
Snjezana Peco updated JBIDE-11267:
----------------------------------
Assignee: Rob Stryker (was: Snjezana Peco)
Component/s: (was: central)
Forum Reference: https://community.jboss.org/message/722946 (was:
https://community.jboss.org/message/722946)
This issue isn't related to central.
Remote Configuration, Runtime Server config missing field
"Remote Configuration"
--------------------------------------------------------------------------------
Key: JBIDE-11267
URL: https://issues.jboss.org/browse/JBIDE-11267
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Reporter: Leo Breuss
Assignee: Rob Stryker
Labels: RSE, runtime
Fix For: 3.3.0.Beta3
In the JBoss Runtime Server configuration, I am no longer able to specify the Remote
Configuration (e.g. standalong-full.xml). It seems like this field has been dropped
between 20111208 and today's 3.3.0b2.
In earlier versions, obviously designed for JBoss 6 and earlier, the implementation of
the JBoss Runtime Server for JBoss 7 had some problems. I'm listing here some of the
problems disucussed in the Forum Reference.
1. The path on the server to look for the existence of the configuration was the
concatenation of <Remote Server Home> + "/server/" + <Remote Server
Configuration>. But JBoss 7 has a different layout structure. No /server/ directory.
2. In the field "Remote Configuration" you should be able to select the
appropriate configuration file from the remote server file system. (Interestingly enough,
the field Remote Server Home can be set by browsing the remote file system.) Instead, one
could browse for a local configuration file, but had to manually strip the absolute path.
Only the filename may remain, because of the concatenation. And the local JBoss
installation has to reflect the remote JBoss regarding the configuration file names. The
default value "default" did not work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:55 p.m.
[
https://issues.jboss.org/browse/JBIDE-11267?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-11267.
---------------------------------
Resolution: Done
Committed to trunk
Remote Configuration, Runtime Server config missing field
"Remote Configuration"
--------------------------------------------------------------------------------
Key: JBIDE-11267
URL: https://issues.jboss.org/browse/JBIDE-11267
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Reporter: Leo Breuss
Assignee: Rob Stryker
Labels: RSE, runtime
Fix For: 3.3.0.Beta3
In the JBoss Runtime Server configuration, I am no longer able to specify the Remote
Configuration (e.g. standalong-full.xml). It seems like this field has been dropped
between 20111208 and today's 3.3.0b2.
In earlier versions, obviously designed for JBoss 6 and earlier, the implementation of
the JBoss Runtime Server for JBoss 7 had some problems. I'm listing here some of the
problems disucussed in the Forum Reference.
1. The path on the server to look for the existence of the configuration was the
concatenation of <Remote Server Home> + "/server/" + <Remote Server
Configuration>. But JBoss 7 has a different layout structure. No /server/ directory.
2. In the field "Remote Configuration" you should be able to select the
appropriate configuration file from the remote server file system. (Interestingly enough,
the field Remote Server Home can be set by browsing the remote file system.) Instead, one
could browse for a local configuration file, but had to manually strip the absolute path.
Only the filename may remain, because of the concatenation. And the local JBoss
installation has to reflect the remote JBoss regarding the configuration file names. The
default value "default" did not work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:06 a.m.
[
https://issues.jboss.org/browse/JBIDE-11267?page=com.atlassian.jira.plugi...
]
Martin Malina updated JBIDE-11267:
----------------------------------
Attachment: standalone-custom-in-server-editor.png
I have this in the server editor:
!standalone-custom-in-server-editor.png!
But in reality the process on the server is using standalone.xml:
{code}
java -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true
-Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000
-Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman
-Djava.awt.headless=true
-Dorg.jboss.boot.log.file=/home/rasp/jbossqa/runtimes/jboss-eap-6.0.0.ER5/standalone/log/boot.log
-Dlogging.configuration=file:/home/rasp/jbossqa/runtimes/jboss-eap-6.0.0.ER5/standalone/configuration/logging.properties
-Djboss.home.dir=/home/rasp/jbossqa/runtimes/jboss-eap-6.0.0.ER5 -jar
/home/rasp/jbossqa/runtimes/jboss-eap-6.0.0.ER5/jboss-modules.jar -mp
/home/rasp/jbossqa/runtimes/jboss-eap-6.0.0.ER5/modules -jaxpmodule
javax.xml.jaxp-provider org.jboss.as.standalone --server-config=standalone.xml
{code}
Remote Configuration, Runtime Server config missing field
"Remote Configuration"
--------------------------------------------------------------------------------
Key: JBIDE-11267
URL: https://issues.jboss.org/browse/JBIDE-11267
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Reporter: Leo Breuss
Assignee: Rob Stryker
Labels: RSE, runtime
Fix For: 3.3.0.Beta3
Attachments: standalone-custom-in-server-editor.png
In the JBoss Runtime Server configuration, I am no longer able to specify the Remote
Configuration (e.g. standalong-full.xml). It seems like this field has been dropped
between 20111208 and today's 3.3.0b2.
In earlier versions, obviously designed for JBoss 6 and earlier, the implementation of
the JBoss Runtime Server for JBoss 7 had some problems. I'm listing here some of the
problems disucussed in the Forum Reference.
1. The path on the server to look for the existence of the configuration was the
concatenation of <Remote Server Home> + "/server/" + <Remote Server
Configuration>. But JBoss 7 has a different layout structure. No /server/ directory.
2. In the field "Remote Configuration" you should be able to select the
appropriate configuration file from the remote server file system. (Interestingly enough,
the field Remote Server Home can be set by browsing the remote file system.) Instead, one
could browse for a local configuration file, but had to manually strip the absolute path.
Only the filename may remain, because of the concatenation. And the local JBoss
installation has to reflect the remote JBoss regarding the configuration file names. The
default value "default" did not work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:22 a.m.
[
https://issues.jboss.org/browse/JBIDE-11267?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-11267:
---------------------------------------
For some reason I cannot reproduce it again for EAP 6 ER 5, but I already reproduced the
above issue for AS 7.1.1 twice. So here are the steps:
1. Prepare your standalone-custom.xml in your AS 7.1.1 server on your remote server -
simply clone standalone.xml
2. Create a remote AS 7.1.1 server. For Remote Server Configuration File set
standalone-custom.xml
3. Start the remote server
4. Check the processes on the remote server - at the end it will have
"--server-config=standalone.xml" - FAIL
Remote Configuration, Runtime Server config missing field
"Remote Configuration"
--------------------------------------------------------------------------------
Key: JBIDE-11267
URL: https://issues.jboss.org/browse/JBIDE-11267
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Reporter: Leo Breuss
Assignee: Rob Stryker
Labels: RSE, runtime
Fix For: 3.3.0.Beta3
Attachments: standalone-custom-in-server-editor.png
In the JBoss Runtime Server configuration, I am no longer able to specify the Remote
Configuration (e.g. standalong-full.xml). It seems like this field has been dropped
between 20111208 and today's 3.3.0b2.
In earlier versions, obviously designed for JBoss 6 and earlier, the implementation of
the JBoss Runtime Server for JBoss 7 had some problems. I'm listing here some of the
problems disucussed in the Forum Reference.
1. The path on the server to look for the existence of the configuration was the
concatenation of <Remote Server Home> + "/server/" + <Remote Server
Configuration>. But JBoss 7 has a different layout structure. No /server/ directory.
2. In the field "Remote Configuration" you should be able to select the
appropriate configuration file from the remote server file system. (Interestingly enough,
the field Remote Server Home can be set by browsing the remote file system.) Instead, one
could browse for a local configuration file, but had to manually strip the absolute path.
Only the filename may remain, because of the concatenation. And the local JBoss
installation has to reflect the remote JBoss regarding the configuration file names. The
default value "default" did not work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:26 a.m.
[
https://issues.jboss.org/browse/JBIDE-11267?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-11267:
---------------------------------------
The same goes for EAP 5.1.2 - even if I set the remote server to start with
"all" configuration, it still starts with "default".
Remote Configuration, Runtime Server config missing field
"Remote Configuration"
--------------------------------------------------------------------------------
Key: JBIDE-11267
URL: https://issues.jboss.org/browse/JBIDE-11267
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Reporter: Leo Breuss
Assignee: Rob Stryker
Labels: RSE, runtime
Fix For: 3.3.0.Beta3
Attachments: standalone-custom-in-server-editor.png
In the JBoss Runtime Server configuration, I am no longer able to specify the Remote
Configuration (e.g. standalong-full.xml). It seems like this field has been dropped
between 20111208 and today's 3.3.0b2.
In earlier versions, obviously designed for JBoss 6 and earlier, the implementation of
the JBoss Runtime Server for JBoss 7 had some problems. I'm listing here some of the
problems disucussed in the Forum Reference.
1. The path on the server to look for the existence of the configuration was the
concatenation of <Remote Server Home> + "/server/" + <Remote Server
Configuration>. But JBoss 7 has a different layout structure. No /server/ directory.
2. In the field "Remote Configuration" you should be able to select the
appropriate configuration file from the remote server file system. (Interestingly enough,
the field Remote Server Home can be set by browsing the remote file system.) Instead, one
could browse for a local configuration file, but had to manually strip the absolute path.
Only the filename may remain, because of the concatenation. And the local JBoss
installation has to reflect the remote JBoss regarding the configuration file names. The
default value "default" did not work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:50 a.m.
[
https://issues.jboss.org/browse/JBIDE-11267?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-11267:
-------------------------------------
Committed to trunk.
A quicker way to test this, without ensuring a full launch, is to open the launch config
for the server. It should show the proper args there. If the args there are wrong, the
launch will be wrong also.
Remote Configuration, Runtime Server config missing field
"Remote Configuration"
--------------------------------------------------------------------------------
Key: JBIDE-11267
URL: https://issues.jboss.org/browse/JBIDE-11267
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Reporter: Leo Breuss
Assignee: Rob Stryker
Labels: RSE, runtime
Fix For: 3.3.0.Beta3
Attachments: standalone-custom-in-server-editor.png
In the JBoss Runtime Server configuration, I am no longer able to specify the Remote
Configuration (e.g. standalong-full.xml). It seems like this field has been dropped
between 20111208 and today's 3.3.0b2.
In earlier versions, obviously designed for JBoss 6 and earlier, the implementation of
the JBoss Runtime Server for JBoss 7 had some problems. I'm listing here some of the
problems disucussed in the Forum Reference.
1. The path on the server to look for the existence of the configuration was the
concatenation of <Remote Server Home> + "/server/" + <Remote Server
Configuration>. But JBoss 7 has a different layout structure. No /server/ directory.
2. In the field "Remote Configuration" you should be able to select the
appropriate configuration file from the remote server file system. (Interestingly enough,
the field Remote Server Home can be set by browsing the remote file system.) Instead, one
could browse for a local configuration file, but had to manually strip the absolute path.
Only the filename may remain, because of the concatenation. And the local JBoss
installation has to reflect the remote JBoss regarding the configuration file names. The
default value "default" did not work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:50 a.m.
[
https://issues.jboss.org/browse/JBIDE-11267?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-11267.
---------------------------------
Resolution: Done
committed
Remote Configuration, Runtime Server config missing field
"Remote Configuration"
--------------------------------------------------------------------------------
Key: JBIDE-11267
URL: https://issues.jboss.org/browse/JBIDE-11267
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Reporter: Leo Breuss
Assignee: Rob Stryker
Labels: RSE, runtime
Fix For: 3.3.0.Beta3
Attachments: standalone-custom-in-server-editor.png
In the JBoss Runtime Server configuration, I am no longer able to specify the Remote
Configuration (e.g. standalong-full.xml). It seems like this field has been dropped
between 20111208 and today's 3.3.0b2.
In earlier versions, obviously designed for JBoss 6 and earlier, the implementation of
the JBoss Runtime Server for JBoss 7 had some problems. I'm listing here some of the
problems disucussed in the Forum Reference.
1. The path on the server to look for the existence of the configuration was the
concatenation of <Remote Server Home> + "/server/" + <Remote Server
Configuration>. But JBoss 7 has a different layout structure. No /server/ directory.
2. In the field "Remote Configuration" you should be able to select the
appropriate configuration file from the remote server file system. (Interestingly enough,
the field Remote Server Home can be set by browsing the remote file system.) Instead, one
could browse for a local configuration file, but had to manually strip the absolute path.
Only the filename may remain, because of the concatenation. And the local JBoss
installation has to reflect the remote JBoss regarding the configuration file names. The
default value "default" did not work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:42 a.m.
[
https://issues.jboss.org/browse/JBIDE-11267?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-11267.
---------------------------------
Resolution: Done
let's just leave this issue as resolved, as the widgets have been put back in and you
already have a new jira open for the null issue.
Remote Configuration, Runtime Server config missing field
"Remote Configuration"
--------------------------------------------------------------------------------
Key: JBIDE-11267
URL: https://issues.jboss.org/browse/JBIDE-11267
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Reporter: Leo Breuss
Assignee: Rob Stryker
Labels: RSE, runtime
Fix For: 3.3.0.Beta3
Attachments: standalone-custom-in-server-editor.png
In the JBoss Runtime Server configuration, I am no longer able to specify the Remote
Configuration (e.g. standalong-full.xml). It seems like this field has been dropped
between 20111208 and today's 3.3.0b2.
In earlier versions, obviously designed for JBoss 6 and earlier, the implementation of
the JBoss Runtime Server for JBoss 7 had some problems. I'm listing here some of the
problems disucussed in the Forum Reference.
1. The path on the server to look for the existence of the configuration was the
concatenation of <Remote Server Home> + "/server/" + <Remote Server
Configuration>. But JBoss 7 has a different layout structure. No /server/ directory.
2. In the field "Remote Configuration" you should be able to select the
appropriate configuration file from the remote server file system. (Interestingly enough,
the field Remote Server Home can be set by browsing the remote file system.) Instead, one
could browse for a local configuration file, but had to manually strip the absolute path.
Only the filename may remain, because of the concatenation. And the local JBoss
installation has to reflect the remote JBoss regarding the configuration file names. The
default value "default" did not work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:51 a.m.
[
https://issues.jboss.org/browse/JBIDE-11267?page=com.atlassian.jira.plugi...
]
Martin Malina closed JBIDE-11267.
---------------------------------
OK, but since I cannot verify this in Beta3, I made a note to myself in the other JIRA to
verify this when verifying that JIRA :)
Closing this issue.
Remote Configuration, Runtime Server config missing field
"Remote Configuration"
--------------------------------------------------------------------------------
Key: JBIDE-11267
URL: https://issues.jboss.org/browse/JBIDE-11267
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Reporter: Leo Breuss
Assignee: Rob Stryker
Labels: RSE, runtime
Fix For: 3.3.0.Beta3
Attachments: standalone-custom-in-server-editor.png
In the JBoss Runtime Server configuration, I am no longer able to specify the Remote
Configuration (e.g. standalong-full.xml). It seems like this field has been dropped
between 20111208 and today's 3.3.0b2.
In earlier versions, obviously designed for JBoss 6 and earlier, the implementation of
the JBoss Runtime Server for JBoss 7 had some problems. I'm listing here some of the
problems disucussed in the Forum Reference.
1. The path on the server to look for the existence of the configuration was the
concatenation of <Remote Server Home> + "/server/" + <Remote Server
Configuration>. But JBoss 7 has a different layout structure. No /server/ directory.
2. In the field "Remote Configuration" you should be able to select the
appropriate configuration file from the remote server file system. (Interestingly enough,
the field Remote Server Home can be set by browsing the remote file system.) Instead, one
could browse for a local configuration file, but had to manually strip the absolute path.
Only the filename may remain, because of the concatenation. And the local JBoss
installation has to reflect the remote JBoss regarding the configuration file names. The
default value "default" did not work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5078
days inactive
5138
days old
jbosstools-issues@lists.jboss.org
11 comments
5 participants
participants (5)
-
Leo Breuss (JIRA) -
Martin Malina (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Rob Stryker (JIRA)
-
Snjezana Peco (JIRA)