Java Web Services and XML
The following sample code is extracted from "Architecture for XML Binding (JAXB) by Ed Ort and Bhakti Mehta, March 2003" to show you a taste of how jaxb coding look like with some of my own comments pepperred in.
You need to plan for performance and scalability through out your application development process, this is not something that can easily be stuck on at the last minute
Software Summit Calls for Papers
Wherein I wander around a Web Services Conference and ask: "Web Services, What Is It Good For?" (and hope that the answer isn't "Huh! Absolutely Nothing").
Suppose you have an USB device and an USB port. How do you connect them? Would you create two adaptors, attach one to the device and one to the port and add extra hardware between them just to get them connected, for no logical reason? Does it seems ridiculous to you? Tell it to most people using webservices out there...
Some thoughts, and links to other discussions, inspired by a speech given by Adam Bosworth last week. Topics touched on include the KISS principle and its breakdown in the XML world, hopes that Father Darwin wil set things right, the challenges of effectively using low-powered mobile devices in an internet optimized for fat pipes, and spins off into a discussion of the ideas behind JXTASpaces as an alternative to the competing distributed object and REST approaches to this kind of application.
some of the latest Web Services "specs" are about
Orchestration, Choreography, Collaboration ...
Here I am going to give a brief synopsis and pointers for more information on this topic.
The latest version of the Java Web Services Developer Pack (JWSDP) 1.3 has just been released.
Web Services are a way for Microsoft to leverage the existing base of J2EE without having to do anything to support Java explicitly.
Java's traditional weapon of choice
Use of XML as a format for exchange of information has its plusses and minuses. XML is self describing and lends itself to more loosely coupled information exchange but it is quite verbose and processing it can be resource intensive. As a result, the subject of a more compact/performant binary representation of XML has become a perma-thread in discussion fora such as xml_dev. In response to this interest, the W3C has announced a Workshop on Binary Interchange of XML Information Item Sets.
XML makes it easier for those who want to agree on a data "standard" to nail down the technical details. On the other hand, when data is sent around or stored in XML, lots of work can be done without agreement or authority.
The acronym SOA for "Services Oriented Architecture" does seem to get tossed around a lot these days. Is this simply the buzzword du jour of the marketers and analysts, or is there something more profound going on here?
When does SOAP add value over just plain HTTP+XML? When you really have to deal with reliable, secure, vendor-neutral, complex applications over multiple networks it definitely beats reinventing a lot of wheels. In simpler situations, your mileage may vary.
Introduction - This weblog will explore some of the alternatives available to Java developers who need to work with XML as documents rather than objects.