+++ This bug was initially created as a clone of Bug #1153960 +++

Handler order can change after a reboot, which causes problems when one handler depends on the action of another.

Solution: The idea is that we need to derive the handlers' order from the add operation steps, which are executed in the same order they're created in the parser.

Brian also suggests to use the OperationContext.attach(...) API to pass data between handler invocations within an overall operation execution. All ws subsystem ops during boot are executed as steps within an overall operation. The API works like the attachment stuff that's used a lot in DeploymentUnitProcessors. 

Details in https://issues.jboss.org/browse/JBWS-3838

--- Additional comment from JBoss JIRA Server on 2014-10-17 09:55:02 EDT ---

Alessio Soldano <asoldano> updated the status of jira JBWS-3838 to Coding In Progress

--- Additional comment from JBoss JIRA Server on 2014-10-24 09:30:29 EDT ---

Alessio Soldano <asoldano> updated the status of jira JBWS-3838 to Open

--- Additional comment from JBoss JIRA Server on 2014-10-24 09:31:25 EDT ---

Alessio Soldano <asoldano> updated the status of jira JBWS-3838 to Resolved