On Tuesday, August 30, 2011 11:55:16 PM dstainer wrote: > Thanks for the quick response Dan. > > I had one additional question about request/response wrapper objects. With > objects coming across the wire you can create immutable objects with the use > of @XmlAccessorType(XmlAccessType.NONE) and private constructors and still > have the objects be marshalled and un-marshalled successfully. > > I'm curious if you can do the same for @RequestWrapper/@ResponseWrapper > objects and if there are any benefits to making those objects immutable or > I'm I over complicating it?
I think you are over complicating it. :-) There really isn't any sort of performance benefit or anything that I'm aware of by doing so, but if it does keep your design cleaner, then by all means, go for it. -- Daniel Kulp [email protected] http://dankulp.com/blog Talend - http://www.talend.com
