[jboss-jira] [JBoss JIRA] (WFWIP-298) Full reload is needed after microprofile-jwt-smallrye subsystem removal
Darran Lofthouse (Jira)
issues at jboss.org
Mon Jan 13 10:29:23 EST 2020
[ https://issues.redhat.com/browse/WFWIP-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13947015#comment-13947015 ]
Darran Lofthouse commented on WFWIP-298:
----------------------------------------
TBH this is just the nature of a subsystem that has registered deployment unit processors, as the subsystem is added and removed a reload is required to ensure the correct set of deployment unit processors are registered and used for the deployments. This is consistent with other subsystems that process deployments.
I know the adding and removing of subsystems is tested regularly but I don't believe this is a prominent feature that end users will be making a lot of use of - if a user is experimenting with adding and removing subsystems I expect they can cope with the reload but I would not be expecting them to make this kind of change on a production installation.
> Full reload is needed after microprofile-jwt-smallrye subsystem removal
> -----------------------------------------------------------------------
>
> Key: WFWIP-298
> URL: https://issues.redhat.com/browse/WFWIP-298
> Project: WildFly WIP
> Issue Type: Bug
> Components: MP JWT
> Reporter: Jan Kasik
> Assignee: Darran Lofthouse
> 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)
More information about the jboss-jira
mailing list