So, one might surmise that Jacquard Loom developers once felt insecure about the goings on in assembler and C development, and that C developers once lost sleep over OO and Java development.

So, supposedly, modern developers in general are living in fear that enterprise SOA directives will take their job away? Not likely feared. Not likely true.

Feared?

If anything, developers are ready to make their systems more efficient and/or agile. Only bad developers want to retain old disgusting decrepit code. Only bad developers like to hamper the efforts of forward thinking change. Don’t get me wrong, there are plenty of bad developers out there. But in the long run, bad developers usually become testers, don’t they? ;-P

True?

SOA is about business agility applied to IT productivity. Downsizing development staff is about as likely as OO reuse once was. If anything, IT staff will swell (and productivity with it).

Most importantly:
“We use an object binding framework,” he explained. “We use XSLT to
transform it in hardware. So when the XML comes in, all the validation,
all the business rules that are applied to it, all the transformations are
done, so we get a clean XML that is exactly fitting the object that we
want. So we can make one Java call, say un-marshal, and we have the
object, lo and behold. We don’t have compiled classes. We have no mapping. Nothing.”

eXist XML Open Source native XML database (mentioned in previous entry):
http://exist.sourceforge.net/

Very cool (eXist example – XQuery sandbox):
http://demo.exist-db.org/sandbox/sandbox.xql