Much more, the data marshalling is done differently. I can contest to its speed, a complex payload of 500k, would take Axis about 12.x seconds to de-serialize, were JiBX is in the 900ms range.
Axis, more like the xml parsers are the bottleneck when it comes to large complex payloads. JiBX solves (http://jibx.sourceforge.net/) please read through his description of the JiBX api set. If he has completed the soap implementation and provided the WSDL conversions it will out perform Axis and JAXB by a mile... Your reply: Hi, I have heard about JiBXSoap on the mailing list a lot and I am interested in it for 2 reasons. One, I recently did some work on Axis and SOAP to improve serialization time by using templates and would want to mention other similar efforts in a document describing my work. Also, I am a bit clueless about what JiBXSoap is about. So, what are the features of JiBXSoap? Does it just generate serializers and deserializers for a given wsdl message type? Or does it do more than that? waiting for reply, ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ jibx-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jibx-users
