Thanks for the response Chris,
Nice to hear that I'm not alone in doubting that buffering of entire
SOAP messages before sending is a must at the server!
I just read something interesting ("Investigating the Limits of SOAP
Performance for Scientific Computing" found at
http://www.extreme.indiana.
In the past I've implemented a gazetteer service with a WFS that simply
auto-detected if the request was wrappen in SOAP (which is just an
envelope if you dont use the intrinsically non-interoperable RPC mode)
and responded with a SOAP wrapper if appropriate.
It is unclear to me where and when
Jonas Johansson wrote:
Hi list,
Maybe someone here has some knowledge on SOAP. I have been looking into
the OGC move towards W3C Web Services standards for geospatial services
and I have a question regarding performance when using SOAP.
It is mentioned by many that large data sets is a perfor
Hi list,
Maybe someone here has some knowledge on SOAP. I have been looking into
the OGC move towards W3C Web Services standards for geospatial services
and I have a question regarding performance when using SOAP.
It is mentioned by many that large data sets is a performance issue when
using SOAP
A short and medium-term fix has been commited on trunk as of revision 19762. It
has been a more
extensive work than I initially planned. Giving the number of changes involved,
it is worth to
perform a "mvn clean" before "mvn install".
The http://docs.codehaus.org/display/GEOTOOLS/The+axis+orde
