[Building Sakai] life after axis report

[Matthew Jones]

Yeah, I think you'd need a deprecation, since it takes some time for local
places to convert over their JWS (some probably have more than others) and
update and external code that's calling it. Sounds like a good change
though.


On Wed, Feb 12, 2014 at 1:28 PM, Charles Severance <csev at umich.edu> wrote:

> 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
>
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140212/254fa128/attachment.html