[
https://issues.jboss.org/browse/JBIDE-2625?page=com.atlassian.jira.plugin...
]
Rob Stryker updated JBIDE-2625:
-------------------------------
Release Notes Text:
Previously, right-clicking a module for AS7 and selecting 'stop' execute an
undeploy, either by a filesystem marker (.undeploy) or by unpublishing the entire module.
Similarly, a 'start' would either add a .deploy or republish the entire
deployment.
Both of these solutions had problems. Republishing an unchanged deployment was wasteful
and took extra time. Using the deployment marker files also required waiting for the
deployment scanners to run.
For AS >= 7, this has changed, and now 'start' and 'stop' closely match
the 'enable' / 'disable' options from the web administration console. The
deployments are started or stopped via the management api, without removing or re-adding
the archive.
This makes start, stop, and restart, much faster than previously. It also solves the user
complaint as posted here.
Fix Version/s: 4.1.0.Alpha2
(was: 4.0.x)
Affects: Release Notes
add an "application stop/application start" option to jboss
server view
-----------------------------------------------------------------------
Key: JBIDE-2625
URL:
https://issues.jboss.org/browse/JBIDE-2625
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS/Servers
Affects Versions: 2.1.2
Reporter: Francisco Jose Peredo Noguez
Assignee: Rob Stryker
Priority: Minor
Labels: new_and_noteworthy
Fix For: 4.1.0.Alpha2
Attachments: web-gui.png
Sometimes, and application just enters an infinte loop (because of a programming error,
because it can not find a class, etc) in those cases one has to stop all the application
server but sometimes, the problem can be solved simply by stopping that particular
application, fixing the problem, and starting it again, and, since one didn't have to
restart Jboss, it takes a lot less time. I would like to be able to do that in an easy way
from inside eclipse.
--
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:
http://www.atlassian.com/software/jira