Bug 1157610

Summary: (6.3.z) JBossWS - SOAP Web Service Handlers executing in different order when server is restarted
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: baranowb <bbaranow>
Component: Web ServicesAssignee: Alessio Soldano <asoldano>
Status: CLOSED CURRENTRELEASE QA Contact: Rostislav Svoboda <rsvoboda>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.3.3CC: asoldano, bbaranow, cdewolf, jawilson, jbliznak, rsvoboda
Target Milestone: CR1   
Target Release: EAP 6.3.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1153960 Environment:
Last Closed: 2019-08-02 07:27:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1153960    
Bug Blocks: 1151405, 1157479    

Description baranowb 2014-10-27 11:20:13 UTC 
+++ 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
Comment 5 Jan Blizňák 2015-01-20 10:24:04 UTC 
Verified on 6.3.3.CP.CR1
Comment 6 JBoss JIRA Server 2015-04-25 20:26:52 UTC 
Alessio Soldano <asoldano> updated the status of jira JBWS-3838 to Closed