4:26 p.m.
Consolidate the remote host configuration for GlassFish Remote
--------------------------------------------------------------
Key: ARQ-269
URL: https://jira.jboss.org/browse/ARQ-269
Project: Arquillian
Issue Type: Feature Request
Components: GlassFish Containers
Affects Versions: 1.0.0.Alpha3
Reporter: Dan Allen
Priority: Minor
Fix For: 1.0.0.Alpha4
In order for the GlassFish Remote container to target a remote host (rather than
localhost), two separate properties must be set:
deploymentUri
remoteServerAddress
The deploymentUri should really be an internal setting, dynamically set based on the
following two configuration values:
remoteServerAddress
remoteServerAdminPort
This hides the more cryptic deploymentUri value and exposes more user-friendly
configuration, less prone to errors.
--
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
8:57 p.m.
New subject: [JBoss JIRA] Updated: (ARQ-269) Consolidate the remote host configuration for GlassFish Remote
[
https://jira.jboss.org/browse/ARQ-269?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen updated ARQ-269:
------------------------------
Fix Version/s: 1.0.0.Beta1
(was: 1.0.0.Alpha4)
Consolidate the remote host configuration for GlassFish Remote
--------------------------------------------------------------
Key: ARQ-269
URL: https://jira.jboss.org/browse/ARQ-269
Project: Arquillian
Issue Type: Feature Request
Components: GlassFish Containers
Affects Versions: 1.0.0.Alpha3
Reporter: Dan Allen
Priority: Minor
Fix For: 1.0.0.Beta1
In order for the GlassFish Remote container to target a remote host (rather than
localhost), two separate properties must be set:
deploymentUri
remoteServerAddress
The deploymentUri should really be an internal setting, dynamically set based on the
following two configuration values:
remoteServerAddress
remoteServerAdminPort
This hides the more cryptic deploymentUri value and exposes more user-friendly
configuration, less prone to errors.
--
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
8:53 a.m.
New subject: [JBoss JIRA] Assigned: (ARQ-269) Consolidate the remote host configuration for GlassFish Remote
[
https://jira.jboss.org/browse/ARQ-269?page=com.atlassian.jira.plugin.syst...
]
Dan Allen reassigned ARQ-269:
-----------------------------
Assignee: Dan Allen
Consolidate the remote host configuration for GlassFish Remote
--------------------------------------------------------------
Key: ARQ-269
URL: https://jira.jboss.org/browse/ARQ-269
Project: Arquillian
Issue Type: Feature Request
Components: GlassFish Containers
Affects Versions: 1.0.0.Alpha3
Reporter: Dan Allen
Assignee: Dan Allen
Priority: Minor
Fix For: 1.0.0.Beta1
In order for the GlassFish Remote container to target a remote host (rather than
localhost), two separate properties must be set:
deploymentUri
remoteServerAddress
The deploymentUri should really be an internal setting, dynamically set based on the
following two configuration values:
remoteServerAddress
remoteServerAdminPort
This hides the more cryptic deploymentUri value and exposes more user-friendly
configuration, less prone to errors.
--
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
1:03 p.m.
New subject: [JBoss JIRA] Commented: (ARQ-269) Consolidate the remote host configuration for GlassFish Remote
[
https://jira.jboss.org/browse/ARQ-269?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen commented on ARQ-269:
-----------------------------------
Do we know 100% that this will always be the case?
GlassFish has a notion of DomainAdminServer, which is responsible for Deploying to the
Nodes. Will the Deployer IP and the 'Testing' Node IP always be the same ?
ARQ-153 will move the removeServerAddress out of the GlassFish container configuration as
a Protocol Configuration as well..
Consolidate the remote host configuration for GlassFish Remote
--------------------------------------------------------------
Key: ARQ-269
URL: https://jira.jboss.org/browse/ARQ-269
Project: Arquillian
Issue Type: Feature Request
Components: GlassFish Containers
Affects Versions: 1.0.0.Alpha3
Reporter: Dan Allen
Assignee: Dan Allen
Priority: Minor
Fix For: 1.0.0.Beta1
In order for the GlassFish Remote container to target a remote host (rather than
localhost), two separate properties must be set:
deploymentUri
remoteServerAddress
The deploymentUri should really be an internal setting, dynamically set based on the
following two configuration values:
remoteServerAddress
remoteServerAdminPort
This hides the more cryptic deploymentUri value and exposes more user-friendly
configuration, less prone to errors.
--
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
12:02 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-269) Consolidate the remote host configuration for GlassFish Remote
[
https://jira.jboss.org/browse/ARQ-269?page=com.atlassian.jira.plugin.syst...
]
Dan Allen commented on ARQ-269:
-------------------------------
Correct, we can't always assume they will be the same. But if they don't provide a
specific remoteServerAdminAddress, then we want to be able to build the deployment URI
using the remoteServerAddress (since that's all the information we have, we assume
it's the same).
What I'm saying in essence is that we should try to assemble the deployment URI
intelligently from bits of facts rather than forcing them to specify that whole cryptic
string. This can all be done in a post-construct method.
Consolidate the remote host configuration for GlassFish Remote
--------------------------------------------------------------
Key: ARQ-269
URL: https://jira.jboss.org/browse/ARQ-269
Project: Arquillian
Issue Type: Feature Request
Components: GlassFish Containers
Affects Versions: 1.0.0.Alpha3
Reporter: Dan Allen
Assignee: Dan Allen
Priority: Minor
Fix For: 1.0.0.Beta1
In order for the GlassFish Remote container to target a remote host (rather than
localhost), two separate properties must be set:
deploymentUri
remoteServerAddress
The deploymentUri should really be an internal setting, dynamically set based on the
following two configuration values:
remoteServerAddress
remoteServerAdminPort
This hides the more cryptic deploymentUri value and exposes more user-friendly
configuration, less prone to errors.
--
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
2:20 p.m.
New subject: [JBoss JIRA] Updated: (ARQ-269) Consolidate the remote host configuration for GlassFish Remote
[
https://issues.jboss.org/browse/ARQ-269?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen updated ARQ-269:
------------------------------
Fix Version/s: 1.1.0.CR1
(was: 1.0.0.Beta1)
Consolidate the remote host configuration for GlassFish Remote
--------------------------------------------------------------
Key: ARQ-269
URL: https://issues.jboss.org/browse/ARQ-269
Project: Arquillian
Issue Type: Feature Request
Components: GlassFish Containers
Affects Versions: 1.0.0.Alpha3
Reporter: Dan Allen
Assignee: Dan Allen
Priority: Minor
Fix For: 1.1.0.CR1
In order for the GlassFish Remote container to target a remote host (rather than
localhost), two separate properties must be set:
deploymentUri
remoteServerAddress
The deploymentUri should really be an internal setting, dynamically set based on the
following two configuration values:
remoteServerAddress
remoteServerAdminPort
This hides the more cryptic deploymentUri value and exposes more user-friendly
configuration, less prone to errors.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:22 p.m.
New subject: [JBoss JIRA] Updated: (ARQ-269) Consolidate the remote host configuration for GlassFish Remote
[
https://issues.jboss.org/browse/ARQ-269?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen updated ARQ-269:
------------------------------
Fix Version/s: glassfish_1.0.0.Beta1
(was: 1.1.0.CR1)
Consolidate the remote host configuration for GlassFish Remote
--------------------------------------------------------------
Key: ARQ-269
URL: https://issues.jboss.org/browse/ARQ-269
Project: Arquillian
Issue Type: Feature Request
Components: GlassFish Containers
Affects Versions: 1.0.0.Alpha3
Reporter: Dan Allen
Assignee: Dan Allen
Priority: Minor
Fix For: glassfish_1.0.0.Beta1
In order for the GlassFish Remote container to target a remote host (rather than
localhost), two separate properties must be set:
deploymentUri
remoteServerAddress
The deploymentUri should really be an internal setting, dynamically set based on the
following two configuration values:
remoteServerAddress
remoteServerAdminPort
This hides the more cryptic deploymentUri value and exposes more user-friendly
configuration, less prone to errors.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:13 a.m.
New subject: [JBoss JIRA] Updated: (ARQ-269) Consolidate the remote host configuration for GlassFish Remote
[
https://issues.jboss.org/browse/ARQ-269?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen updated ARQ-269:
------------------------------
Fix Version/s: glassfish_1.0.0.Final
(was: glassfish_1.0.0.CR1)
Consolidate the remote host configuration for GlassFish Remote
--------------------------------------------------------------
Key: ARQ-269
URL: https://issues.jboss.org/browse/ARQ-269
Project: Arquillian
Issue Type: Feature Request
Components: GlassFish Containers
Affects Versions: 1.0.0.Alpha3
Reporter: Dan Allen
Assignee: Dan Allen
Priority: Minor
Fix For: glassfish_1.0.0.Final
In order for the GlassFish Remote container to target a remote host (rather than
localhost), two separate properties must be set:
deploymentUri
remoteServerAddress
The deploymentUri should really be an internal setting, dynamically set based on the
following two configuration values:
remoteServerAddress
remoteServerAdminPort
This hides the more cryptic deploymentUri value and exposes more user-friendly
configuration, less prone to errors.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:07 p.m.
New subject: [JBoss JIRA] Resolved: (ARQ-269) Consolidate the remote host configuration for GlassFish Remote
[
https://issues.jboss.org/browse/ARQ-269?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen resolved ARQ-269.
-------------------------------
Resolution: Done
removed the need for the duplicate registration, pushed upstream:
https://github.com/arquillian/arquillian-container-glassfish/commit/3d3d1...
Consolidate the remote host configuration for GlassFish Remote
--------------------------------------------------------------
Key: ARQ-269
URL: https://issues.jboss.org/browse/ARQ-269
Project: Arquillian
Issue Type: Feature Request
Components: GlassFish Containers
Affects Versions: 1.0.0.Alpha3
Reporter: Dan Allen
Assignee: Dan Allen
Priority: Minor
Fix For: glassfish_1.0.0.Final
In order for the GlassFish Remote container to target a remote host (rather than
localhost), two separate properties must be set:
deploymentUri
remoteServerAddress
The deploymentUri should really be an internal setting, dynamically set based on the
following two configuration values:
remoteServerAddress
remoteServerAdminPort
This hides the more cryptic deploymentUri value and exposes more user-friendly
configuration, less prone to errors.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:37 p.m.
New subject: [JBoss JIRA] (ARQ-269) Consolidate the remote host configuration for GlassFish Remote
[
https://issues.jboss.org/browse/ARQ-269?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen updated ARQ-269:
------------------------------
Fix Version/s: glassfish_1.0.0.CR2
(was: glassfish_1.0.0.Final)
Consolidate the remote host configuration for GlassFish Remote
--------------------------------------------------------------
Key: ARQ-269
URL: https://issues.jboss.org/browse/ARQ-269
Project: Arquillian
Issue Type: Feature Request
Components: GlassFish Containers
Affects Versions: 1.0.0.Alpha3
Reporter: Dan Allen
Assignee: Dan Allen
Priority: Minor
Fix For: glassfish_1.0.0.CR2
In order for the GlassFish Remote container to target a remote host (rather than
localhost), two separate properties must be set:
deploymentUri
remoteServerAddress
The deploymentUri should really be an internal setting, dynamically set based on the
following two configuration values:
remoteServerAddress
remoteServerAdminPort
This hides the more cryptic deploymentUri value and exposes more user-friendly
configuration, less prone to errors.
--
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:41 p.m.
New subject: [JBoss JIRA] (ARQ-269) Consolidate the remote host configuration for GlassFish Remote
[
https://issues.jboss.org/browse/ARQ-269?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen closed ARQ-269.
-----------------------------
Consolidate the remote host configuration for GlassFish Remote
--------------------------------------------------------------
Key: ARQ-269
URL: https://issues.jboss.org/browse/ARQ-269
Project: Arquillian
Issue Type: Feature Request
Components: GlassFish Containers
Affects Versions: 1.0.0.Alpha3
Reporter: Dan Allen
Assignee: Dan Allen
Priority: Minor
Fix For: glassfish_1.0.0.CR2
In order for the GlassFish Remote container to target a remote host (rather than
localhost), two separate properties must be set:
deploymentUri
remoteServerAddress
The deploymentUri should really be an internal setting, dynamically set based on the
following two configuration values:
remoteServerAddress
remoteServerAdminPort
This hides the more cryptic deploymentUri value and exposes more user-friendly
configuration, less prone to errors.
--
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
4588
days inactive
5006
days old
arquillian-issues@lists.jboss.org
10 comments
4 participants
participants (4)
-
Aslak Knutsen (Closed) (JIRA) -
Aslak Knutsen (JIRA)
-
Aslak Knutsen (Updated) (JIRA)
-
Dan Allen (JIRA)