Axis2

[steel]

Now that Axis2 is released and the performance improvement is drastic compared to Axis1, are there plans to migrate the current WS implementation to Axis2?

[davidc]

We'll move away from Axis v1 for sure.  However, given our experience so far with Axis, moving to v2 is not too attractive.  It may have been re-written, but we still need to be convinced.  There are plenty of other WS stacks such as XFire that have our attention.

If anyone has good/bad experience of WS stacks they'd like to share with us, we're listening.

[steel]

I am testing an app right now to import content to the Alfresco Repo via WS and I am encountering OutOfMemoryError: Java heap space.  I am using the Axis1 client. My profiler reports that the Axis Client is consuming 78% of the cpu cycles and is also using over 250MB of ram.  It seems that Axis 1 just isn't very efficient as this out of memory error occurs even when I have -Xmx1024m set. My application is importing multi-hundred megabyte contents.

Should I move away from Axis1 as a client. Any recommendations?  I was investigating Axis2, and now Xfire.

thanks.

[steel]

It seems that the Axis1 WS Stack runs out of heap space if tries to write content that is larger than 32MB. It doesn't matter how large the JVM heap size is. 512MB, 1024MB, Out of memory still occurs.  I am using the latest 1.4 Axis.  So as a temporary fix, my app has a content size limitation of 32MB.  I am using Java 1.4 so the stub generation for XFire won't work and the stubs generated by Axis2 are not complete.