Bug 1153960

Summary: (6.4.0) JBossWS - SOAP Web Service Handlers executing in different order when server is restarted
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Rostislav Svoboda <rsvoboda>
Component: Web ServicesAssignee: Alessio Soldano <asoldano>
Status: CLOSED CURRENTRELEASE QA Contact: Rostislav Svoboda <rsvoboda>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.4.0CC: bbaranow, jbliznak, kkhan
Target Milestone: DR10   
Target Release: EAP 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1157610 (view as bug list) Environment:
Last Closed: 2019-08-02 07:30:32 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:    
Bug Blocks: 1153972, 1157610    

Description Rostislav Svoboda 2014-10-17 08:05:22 UTC 
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
Comment 1 JBoss JIRA Server 2014-10-17 13:55:02 UTC 
Alessio Soldano <asoldano> updated the status of jira JBWS-3838 to Coding In Progress
Comment 2 JBoss JIRA Server 2014-10-24 13:30:29 UTC 
Alessio Soldano <asoldano> updated the status of jira JBWS-3838 to Open
Comment 3 JBoss JIRA Server 2014-10-24 13:31:25 UTC 
Alessio Soldano <asoldano> updated the status of jira JBWS-3838 to Resolved
Comment 4 Kabir Khan 2014-11-10 18:32:53 UTC 
See component upgrade https://bugzilla.redhat.com/show_bug.cgi?id=1153972#c2 for explanation of why the upgrade was reverted and this BZ is set back to ASSIGNED
Comment 5 Jan Blizňák 2014-11-20 12:05:01 UTC 
Verified on 6.4.0.DR10
Comment 6 JBoss JIRA Server 2015-04-25 20:26:52 UTC 
Alessio Soldano <asoldano> updated the status of jira JBWS-3838 to Closed