Cocoon and Axis

[Matthew Langham <ml...@sundn.de>]

Hi,

I just posted the following to the Axis mailing list - so this is FYI.

>>
Axis is currently the "Soap engine" of choice in the Cocoon project an we
have now started to use this duo in a real-world application and came
accross several issues that prevented us from getting something up and
running (proxy, Apache Soap 2.2 Vector). These problems we sent to the list
but received little (or no) reply.

So in the end we fixed the things ourselves and Carsten submitted these
patches (httpProxy, VectorDeserializer) - but they seem to take long to make
it into the distribution (the VectorDeserializer is still not there) - why
is this? Over on the Cocoon project we are used to short submittal cycles
and find the Axis project be rather slow when it comes to this.

I think that in order to get Axis into real world scenarios (if that is the
goal) the project needs to put more emphasis on these types of problems in
addition to what Sanjiva writes (and I agree on his points).

So - what is the answer? Should Cocoon switch back to using Apache Soap 2.x?
<<

Matthew

--
Open Source Group               sunShine - Lighting up e:Business
=================================================================
Matthew Langham, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
Tel: +49-5251-1581-30   [mlangham@sundn.de - http://www.sundn.de]
=================================================================



---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org