[jboss-jira] [JBoss JIRA] (WFLY-7300) OperationHandlers that register DeploymentProcessor should do it only on boot

[James Perkins (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-7300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13337336#comment-13337336 ] 

James Perkins edited comment on WFLY-7300 at 12/12/16 1:14 PM:
---------------------------------------------------------------

I was able to duplicate this with the legacy {{batch}} subsystem. This is my fault as I was testing this with some other batch changes I'm working that includes a fix for this. I can either do a quick patch for this or we can wait, hopefully just this week, until I can send in a PR with other changes that will fix this.

As far as a workaround goes if the {{batch-jberet}} subsystem is used the issue should disappear. The {{batch}} subsystem is deprecated anyway.


was (Author: jamezp):
I was able to duplicate this with the legacy {{batch}} subsystem. This is my fault as I was testing this with some other batch changes I'm working that includes a fix for this. I can either do a quick patch for this or we can wait, hopefully just this week, until I can send in a PR with other changes that will fix this.

> OperationHandlers that register DeploymentProcessor should do it only on boot
> -----------------------------------------------------------------------------
>
>                 Key: WFLY-7300
>                 URL: https://issues.jboss.org/browse/WFLY-7300
>             Project: WildFly
>          Issue Type: Bug
>            Reporter: ehsavoie Hugonnet
>            Assignee: James Perkins
>             Fix For: 11.0.0.Alpha1
>
>
> Registering a DeploymentProcessor is a boot only operation. Thus instead of extends AbstractAddStepHandler they should extend  AbstractBoottimeAddStepHandler



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)