Re: "Uh, what do I need this for" (was RE: XML.COM: How I LearnedtoLove
Leigh Dodds wrote: > One side effect of immutable Value objects I noted recently when > adding a SOAP interface to one of our components, was that I couldn't > take advantage of the Apache SOAP support for automated (de-)serialisation > of JavaBeans. Value objects aren't JavaBeans because everything is > done in the constructor, and there are no set methods. The cure for that is to add a volatile boolean xxxIsSet field for every regular field. The normal constructor sets all these to true, whereas the Bean (parameterless) constructor sets them all to false. Each setXxx method throws an Error if xxxIsSet is true; otherwise it sets the regular field to the given value and xxxIsSet to true. This gives immutable semantics while being bean-serialization compatible, since the deserializer calls each set method exactly once. It would be useful to write a preprocessor to insert the xxxIsSet fields and the setXxx methods. -- Not to perambulate || John Cowan <jcowan@r...> the corridors || http://www.reutershealth.com during the hours of repose || http://www.ccil.org/~cowan in the boots of ascension. \\ Sign in Austrian ski-resort hotel
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format