-
Feature Request
-
Resolution: Done
-
Major
-
EAP 5.0.0, EAP 5.0.1, EAP_EWP 5.1.0, EAP_EWP 5.1.1
-
None
-
Release Notes
-
-
Documented as Resolved Issue
-
NEW
Currently, many customers use the MainDeployer MBean to deploy applications to EAP from the command line. It's been a part of the application server for many years.
In EAP 5, it is still available, but in many cases it behaves in a broken manner. Furthermore, deployment via the MainDeployer is not the same as deployment via the deploy subdiretory (it was the same before) or the Admin console. This makes things very confusing.
This feature request is to re-implement the MainDeployer MBean with ProfileService API backing. The goal would be to mimic EAP 4.x behavior as close as possible. Backwards compatibility shouldn't be a concern as much of it is broken in EAP 5 already. What does work can be unit tested, etc.
- blocks
-
JBPAPP-7330 JMXInvokerTestCase and secureJMXInvokerTestCase fails on all Windows platform
- Closed