]
Rob Stryker commented on JBIDE-16721:
-------------------------------------
I should clarify my statement. I was pushing off these requests to beta2, not pushing to
the beta2 repo ;)
As for an your comments, I will change the strings in beta1, and I will change the
parenthesis comment to read "Use Management Operations" instead of prefers. But
no, it cannot be just a checkbox. It must be a profile based on underlying architecture.
Sorry.
Made a commit to beta2.
Language change is included in
for beta1x branch.
Creation of 2 additional profiles for use with as7/wf
-----------------------------------------------------
Key: JBIDE-16721
URL:
https://issues.jboss.org/browse/JBIDE-16721
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: server
Affects Versions: 4.2.0.Alpha2
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.2.0.Beta2
With so many options available, more profiles need to be added to ensure that servers are
created correctly, with all settings appropriate, out of the box. For this reason, we will
now have 4 profiles:
1) Local
2) Local (Prefers Management Operations)
3) Remote
4) Remote (Prefers Management Operations)
The differences between 1 and 2 are minimal. The server will start via a java launch, and
shutdown via management, however, the new managed deployment page will show instead of the
old UI.
For 3 vs 4, though, there are several differences. First, in 3), the remote management
port will not be exposed. The pollers will be web-port pollers (instead of mgmt pollers),
and the shutdown will execute a command over rse. Deployment will be filesystem based over
ssh.
In 4), however, mgmt port will be exposed, shutdown will use mgmt api, pollers will be
mgmt pollers. Deployment will be using management api.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: