in 4) you should check if there's a WebServicesMetaData attachment; if that's the case, you need to update the existing one, otherwsise the data in it would be lost
Yes, that makes sense. I couldn't find a reference to webservices.xml in the JAX-WS spes. Is this just a JAX-RPC feature?
It's actually a JSR 109 concept; the webservices.xml is mandatory for JAX-RPC and optional for JAX-WS.
regarding your logic for updating the WS_ENDPOINT_HANDLERS_MAPPING_KEY instead, I believe you should have that run after Phase.PARSE_JAXWS_HANDLER_CHAIN_ANNOTATION but before Phase.PARSE_JAXWS_HANDLER_CREATE_COMPONENT_DESCRIPTIONS, as there's a DUP registered at that phase which should be reading the data. You might need to shift Phase.PARSE_JAXWS_ENDPOINT_CREATE_COMPONENT_DESCRIPTIONS and Phase.PARSE_JAXWS_HANDLER_CREATE_COMPONENT_DESCRIPTIONS values down a bit, just be sure to keep the rest of the ordering.
I think this is what I have with the following?
| public static final int PARSE_JAXWS_HANDLER_CHAIN_ANNOTATION | = 0x2055; |
| public static final int PARSE_TXFRAMEWORK_HANDLERS | = 0x2056; |
| public static final int PARSE_WS_JMS_INTEGRATION | = 0x2057; |
| public static final int PARSE_JAXWS_ENDPOINT_CREATE_COMPONENT_DESCRIPTIONS | = 0x2058; |
| public static final int PARSE_JAXWS_HANDLER_CREATE_COMPONENT_DESCRIPTIONS | = 0x2059; |
Perfect, this is what I meant.
to answer your question on the actual need for populating WS_ENDPOINT_HANDLERS_MAPPING_KEY attachment, yeah, that's required for having the AS7 components properly created for your handlers too.
What AS7 components do you mean here?
I'm referring to the AS7 org.jboss.as.ee.component.ComponentDescription . The org.jboss.as.webservices.deployers.WSIntegrationProcessorJAXWS_HANDLER that's registered at Phase.PARSE_JAXWS_HANDLER_CREATE_COMPONENT_DESCRIPTIONS uses the WSEndpointHandlersMapping data for propagating the naming context in the component descriptors.