[ https://jira.jboss.org/jira/browse/JBWS-2386?page=com.atlassian.jira.plug... ] Richard Opalka updated JBWS-2386: --------------------------------- Summary: Investigate JBossWS SAAJ impl decoupling from JBossWS Core (was: Decouple JBossWS SAAJ impl from JBossWS Core) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBWS-2386?page=com.atlassian.jira.plug... ] Richard Opalka commented on JBWS-2386: -------------------------------------- This would be really complicated because JBossWS SAAJ impl has hardcoded dependencies on: * JBossWS extensions (e.g. MTOM, see SOAPElementContent for example) * JAXWS (see SOAPContentElement for example) * has hardcoded dependencies on JBossWS UMDM (EndpointMetadata, OperationMetadata, ParameterMetadata, see SOAPMessageImpl for example). * ThreadLocals that are JBossWS stack native dependent (see SOAPContentElement for example) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira