Comments on: SAAJ ruined

By: The Ancient Art of Programming » The Sorry State of SAAJ

The Ancient Art of Programming » The Sorry State of SAAJ — Mon, 19 May 2008 00:36:57 +0000

[...] extends Element, and so on, and so forth. Not everybody thought this was a clever idea; clearly Hani was not among those in favor. At this point, SAAJ was added to J2EE 1.4. Some J2EE vendors seem to [...]

By: Prasad Chodavarapu

Prasad Chodavarapu — Sat, 16 Aug 2003 02:44:22 +0000

Trackback doesn’t seem to be enabled. Here’s a related entry in my weblog.
http://ramya.bhaavana.net/chaitanya/archives/000015.html

By: pankaj kumar

pankaj kumar — Wed, 18 Jun 2003 02:45:55 +0000

In fact, I had the reverse problem with original SAAJ. It invented its own DOM API for SOAP messages and in the process, made it extremely inefficient to use libraries that expected W3C DOM structure. The specific library I am referring to is XML Signature and XML Encryption from VeriSign. And now, even the public draft of XML Signature Java API uses DOM structure.
So, if we want to leverage XML infrastructure for SOAP, we better accept that a SOAP message is an XML message.

By: Marc Logemann

Marc Logemann — Sat, 14 Jun 2003 19:55:32 +0000

kSoap?

By: fx

fx — Thu, 12 Jun 2003 11:44:57 +0000

So what do they use, the mobile device java programmers?

By: Fred Grott

Fred Grott — Thu, 12 Jun 2003 10:52:44 +0000

I would say if you seetle for SAAJ you di not look hard enough :)

Of course you may have been search at a time when other good soap implementations may not been out there..

Next tim e if it come sup look for what mobile device java programmers are using becuase they have the saem size and perfomance needs as you do :)

By: Chiara

Chiara — Thu, 12 Jun 2003 02:54:52 +0000

Hani,
you are one of a kind. We were ready for your honesty and breath of fresh air. Thanks for an amazing set of blogs so far. I can’t wait to read what you write everyday.. Please don’t lose this tone.. Say it as it is brother..

;)