--
Julien Cassignol
http://www.ainulindale.net
I have a look at the source though and it seems to me that you're
doing about the same thing I do, that is for my example:
Create a context
Create a AProxy
Context-Edit BProxies settable on A
Set BProxies on A
Persist.
This goes well for me up to the point of the construction of the
Domain object. As I was saying, my A object has all the attributes
supposed to be there BUT for the other entity proxies (in my case A
has a name but no B).
I didn't manage to find out where this was set in the labyrinthic
sources, and I'm wondering if this could not be due to a
misunderstanding on my side of the proper annotations I should set on
my domain objects.
In this specific case all objects are EntityProxy (no ValueProxy) and
all have proper primary keys.
B objects are currently properly retrieved from the database and
populate a SuggestBox. When I try to use
((MySuggestions<BProxy>)event.getSelectedItem()).getEntity() (using a
custmo SuggestionSelection which keeps the entityproxy) I can get the
proper entity and I can set it to my AProxy object.
The problem resides between the fire() call (which according to
inspect contains the proper values of the AProxy) and the actual DAO
call in which I have my A object with all the values but for the
values of the proxified B objects.
I'm not sure I'm clear enough :-)
I forgot that during the whole setup I kept using TODOs methods in my
DAO. Namely, one used by the Locator to retrieve objects with the
find() method.
As the DAO methods kept returning null, the mapping kept setting a
null value to my domain object. Implementing the method solved the
problem and the mapping went as supposed.
PEBKAC in the end :-)