[
https://issues.redhat.com/browse/WFLY-12980?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFLY-12980:
-----------------------------------------
This should be rejected. Subsystems that require deployment unit processors require a
reload. Users should evaluate their configuration in a non-production environment.
If there is a high likelihood users would not notice this subsystem in their config and
then feel an urgent need to remove it in production, i.e. not as part of a normal
maintenance cycle that would bounce their deployments, then we should look into why they
would feel that need and either fix whatever that problem is, or if it's inherent in
the subsystem, reevaluate having it in the standard configuration. But I'm not aware
of any problems like that. Is anyone else?
Full reload is needed after microprofile-jwt-smallrye subsystem
removal
-----------------------------------------------------------------------
Key: WFLY-12980
URL:
https://issues.redhat.com/browse/WFLY-12980
Project: WildFly
Issue Type: Bug
Components: MP JWT
Reporter: Jan Kasik
Priority: Major
When user is removing MP subsystem, full reload is required. This is partly a benefit
because it provides a fast fail solution for deployments which requires classes from this
subsystem. On the other hand, reload might not be feasible for user under in their current
conditions. This is why it has to be reduced as much as possible.
Is there other way to provide fast fail without requiring full reload?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)