i have just committed my initial changes to the XMLDatabinder class.  now
un-initialised proxies and lazy collections can be left un-initialised.

this behaviour is controlled by the new private boolean field traverseLazy.
for now it is set to true, to reflect the behaviour of this class to date.
i have not provided a mechanism to configure this yet.  i am leaning towards
changing openDatabinder() on SessionFactory to openDatabinder(boolean
traverseLazy).

i have also added the proxy attribute to the property element for an entity
that has a proxy (and the lazy attribute for collections with similar
behaviour).  it can have the values:
  un-initialized
  initialized
  now-initialized - this is set if the proxy was un-initialized and we
initialized the proxy

brad



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel

Reply via email to