I have submitted the patch that works in my configuration.  There are two
updated files with only a few new/changed lines of code.  I read elsewhere
that Vincent is out for a few weeks, so I don't know when it would make it
into the CVS tree (if ever).  For now, you can use the patch from the
"patches" page.

In it's final form, I imagine there will be a check for bidirectionality at
the method-tag level before requiring the new get*Value(Map) methods.  For
now, these methods are absolutely required.

Andrew

> On Wed, 2002-07-10 at 16:15, Vincent Harcq wrote:
 >
 >>Hi,
 >>
 >>First, because an entity bean -must- run inside a transaction:
 >>Is there anyway to identify the running transaction ?  I remember
 >>something like a JNDI lookup to java:/UserTransaction but this only
 >>works for BMT.  Does something else exist to get access to the
 >>Transaction ID ?
 >>
 >>Then we can store this in the VO and simply return at the beginning of a
 >>VO getter if we are in the same transaction as the one saved in the VO.
 >>
 >>Second, I think the same problem occurs for CMP2 container vendors for
 >>bidirectionnal relationship.  Of course they run inside the container so
 >>  they have access to the Transaction.  This is more simple.  For
 >>MVCSoft that runs outside the container the problem is still there,...,
 >>except of course if it generate BMT BMP.  Any thoughts are welcome here.
 >>
 >>Third, and the most important in fact ;).  How would you solve your case
 >>if xdoclet did not exist ?
 >>
 >>Vincent.
 >>
 >>Colin Daly wrote:
 >>
 >>>Hi all,
 >>>
 >>>i've been playing with the new value objects and i got quite excited
 >>>by the new (aggregate/compose) relationship handling (Excellent job
 >>>Vincent). We have quite a deep, complicated graph of value objects which
 >>>we currently construct and deconstruct manually. The code is thousands
 >>>of lines long and is tedious, repetitive and error prone. The value
 >>>objects could blow away all of this except for one "little" problem.
 >>>They don't seem to handle bi-directional relationships. I tried it and
 >>>ended up with StackOverflowExceptions.
 >>>The problem is illustrated in the xdoclet samples themselves -
 >>>the following methods (getCustomerValue() and getAccountValue()) are
 >>>from the samples generated source files CustomerCMP and AccountCMP
 >>>respectively. There is a 1-N bidirectional aggregate relationship
 >>>between Customer and Account. As you can see, there is a problem.
 >>>Craig (a colleague) and I have had a chat about the problem and
 >>>there doesn't appear to be any quick fix. Hopefully this mail
 >>>will start a discussion and we will find a solution.
 >>>
 >>>Colin Daly.


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

Reply via email to