Wednesday, August 10, 2005
CoolBeans revealed
So CoolBeans are about technology, software, gadgets and thoughts that tend to coolness.
Also, short quotations from the work of Raymond Lin (RL), my distinguished colleague whose words are sometimes more than truth.
http://wiki.bonsaitalk.com/index.php/Coolbeans
CoolBeans: XMLBeans, JAX-RPC and Serialization
These three technologies (among others) have something in common. A feature that is easily overlooked, but still vital to smart computing.
Let’s define first:
Serialization: An act of writing objects onto a medium in a serial, byte-by-byte manner. In Java, any object that can do this has to at least implement mark-up interface java.io.Serializable. Any referenced objects have to be Serializable and will be serialized altogether.
JAX-RPC: Java API for XML-based RemoteProcedureCall. You may have sensed the tie-in to serialization via the RPC portion of the acronym, but that’s not the main reason it is here. Rather, we think of mapping of the Objects to SOAP (SimpleObjectAccessProtocol) messages for RPC call (webservice). We think of the mechanism we map Objects and primitive types into SOAP.
XMLBeans: Java-XML binding tool. The XML schema is converted into set of Java classes representing elements. Inheritance and Composition is used to reflect nested elements and document structure. XML nodes can be manipulated via accessors and mutators of particular java object.
The common feature is the ability to create an object tree that decomposes any Object into its smaller and smaller denominators. Serializable object is serializable only when all the nested and referenced objects are serializable too. All building blocks of an object will be serialized one by one, thus creating basic object tree. JAX-RPC also creates SOAP elements by decomposition mechanism and XMLBeans go even further by naming it right. Generally, the basic building block is an object with certain properties (preferably primitive) and accessors and mutators. A JavaBean.
JavaBeans are very powerful concept because of its decomposition capabilities and the ability to shift our focus from the complexities of a system towards the real nature and desired functionality of the system. In Fit testing (testing of business requirements before any code is written), anything is a JavaBean to begin with, be it a Host System, Java Object or database. This fine decomposition gives us very interesting and important view at the overall system, uncluttered of the “complexities”.
This also enforces the rule that healthy object has properties and responsibilities that belong only to this object; otherwise decomposition into simple object tree is not possible. That’s how we get to the very basics again.
http://java.sun.com/docs/books/tutorial/essential/io/serialization.html
http://dev2dev.bea.com/xml/xmlbeans.csp
http://java.sun.com/xml/jaxrpc/index.jsp
Wednesday, August 03, 2005
Damn you Random!
RL Aug 02 05
Wednesday, March 30, 2005
Easter spirit
The sermon tonight: "Searching for Jesus.
Thursday, March 10, 2005
The coffee Oracle
There's been a friction this morning. It's not her, it's me. I keep changing my orders, oscillating the orbit of x-large peppermint tea, large black coffee, steeped tea and occasionally large double double (cream and sugar) coffee. With no apparent pattern in my choices whatsoever. My order of medium coffee AND sour cream glazed donut turned her into tailspin today. She was clearly not ready for it. Being a soldier she is, she filled my order and gave me my change back. While finishing the transaction, she looked at me with utter disbelief and asked: "Are you sure this is for you?".
Another person's day and possibly dreams shattered...