Unfortunately, there is no way to remove the synchronized blocks from the generated getters and setters. But, you can pass in the option XmlOptions.setUnsynchronized() when creating the XmlBeans objects and that will remove synchronization everywhere else. Then, maybe the remaining overhead is acceptable.
Radu On Mon, 2008-05-19 at 17:39 -0700, fastbob wrote: > > Howdy, > I have been looking into performance issues for a system using > xmlbeans. > This system only uses xmlbeans in the context of a single thread, so > it > would seem the "synchronized (monitor())" calls in the getters and > setters > add a bit of unnecessary overhead. > > Is there a mechanism to suppress generating such code? Or am I wrong > in my > assessment? > > Thanks. > > Bob > -- > View this message in context: > http://www.nabble.com/Suppressing-synchronize--tp17331053p17331053.html > Sent from the Xml Beans - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
