Yes, there IS some overhead associated with XML parsing, but XML parsers can
be very efficiently designed for the kind of things SOAP needs (see the XML
library of http://www.themindelectric.com), and as I learnt early on when
doing my first steps with EJB, you'd better limit the number of accesses to
EJB's anyway. I mean: doing RMI isn't that cheap either. So...
And there's another big advantage of using SOAP: it's all the associated
technologies that come with it, like UDDI and WSDL. BTW, I'm not sure wether
ebXML is a concurrent candidate for the things those two technologies
address. And if it is, it might well be that they already lost the battle...
WSDL allows for automatic documentation of SOAP services, which can be
gathered from the sources and Javadoc. UDDI lets you publish information
about your company's activities and ultimately lets your potential customers
access your WSDL documented SOAP services without having ever met you. This
is just great, and a very nice opportunity for EJB developers to capitalize
on their work. What I foresee from the .NET side is that, if M$ is smart
enough (and believe me, they are), they could just make deployment wizards
which allow their developers to publish their services to UDDI right away.
That's coming to us in the form of the WASP tools for NetBeans for example,
and I think it's a very good initiative. The problem is that Idoox (the
people who made WASP - what an horrible name btw!!!) licenses its WASP
runtime for quite an amount of money, which is not the case for .NET (free
!).
I think that we need tools like the WASP ones, and more SOAP/WSDL/UDDI/EJB
runtimes that are compatible with Java.
What do you think ?
Candide
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
