[jira] Resolved: (WSCOMMONS-86) Separate SOAP impl from core Axiom

["Andreas Veithen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WSCOMMONS-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Veithen resolved WSCOMMONS-86.
--------------------------------------

    Resolution: Won't Fix

This issue has been open for more than two years now. During that time, there have been no votes or additional comments to support this request. Also, while in the early days of Axiom, separating the SOAP specific part from the rest would probably have had a positive impact on the design, I think that today it would be quite difficult to achieve this without impacting some of the APIs and therefore existing code that uses Axiom. Finally, as Eran pointed out, we would have to split Axiom into 6 different artifacts (instead of 3 now), which is probably an overkill for a project like Axiom. For these reasons, I'm going to close this issue.

> Separate SOAP impl from core Axiom
> ----------------------------------
>
>                 Key: WSCOMMONS-86
>                 URL: https://issues.apache.org/jira/browse/WSCOMMONS-86
>             Project: WS-Commons
>          Issue Type: Improvement
>          Components: AXIOM
>         Environment: All
>            Reporter: James M Snell
>
> Some applications (such as Apache Abdera) which utilize Axiom as an XML Infoset implementation have no need for the SOAP classes.  Some mechanisms, such as the ability to set a DataHandler on an Element and have that automatically Base64 encoded is very useful and should be kept in the Axiom core, but things like the soap packages and mtom could/should be moved out to a separate jar.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.