[Building Sakai] life after axis report
Charles Severance
csev at umich.edu
Wed Feb 12 10:28:24 PST 2014
I am cool with deprecating Axis1 for -10. For me, removal on -11 would depend on having decent coverage of the jws capabilities in new CXF services - which sounds like it won't be too hard to do.
/Chuck
On Feb 12, 2014, at 9:13 AM, Sam Ottenhoff <ottenhoff at longsight.com> wrote:
> Right, SOAP webservices are disabled by default. The new CXF webservices respect this same property.
>
> I think we should deprecate the Axis1 webservices, add the CXF code, modify our documentation to recommend the new CXF endpoints if they need to continue using these methods. Then we can remove Axis1 from Sakai 11. Objections?
>
> CXF also seems more performant. I did a quick test: create 2000 users, enroll them into a project site, and CXF SOAP webservices were about 10% faster than the same Axis1 methods.
>
> --Sam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140212/5c870cb4/attachment.html
More information about the sakai-dev
mailing list