#: Christophe Lombart changed the world a bit at a time by saying on 1/3/2006
3:10 PM :#
On 1/3/06, Alexandru Popescu <[EMAIL PROTECTED]> wrote:
As you figured it out, I am using directly the ObjectConverter. I have created
a few util classes to
have everything configured from Spring.
I'm going to commit in a couple of days (maybe tomorrow), the spring support.
It is finish but I have to make more test. This is based on the work
make by one of the spring module commiter.
Are you talking about Costin (Leau) ? Can you please send it to me, to compair
it with my version?
Now, about the scenario: imagine a service that is working with different node
subtrees, but these
are related, either by their content, or by their references. In this case I
need to pass around
different information (and not all of it is stored in my model, but sometimes
is available only in
the node itself). In this scenario after each insert/update i need to get my
hand on the
inserted/updated node.
Does it make any sense to you?
well, the current framework gives you a way to work *only* on the model level.
If I understand, you want to read or modify the nodes created by the
objectConverter after an insert - is is correct ? Is it not something
like a post process after inserting, updating, .. an object ?
Yes, that's it.
./alex
--
.w( the_mindstorm )p.
christophe
./alex
--
.w( the_mindstorm )p.
> On 1/3/06, Alexandru Popescu <[EMAIL PROTECTED]> wrote:
>> Hi again!
>>
>> I was trying to figure out if changing the ObjectConverter interface to
return the inserted/updated
>> node would make sense. I have scenarios where I would like to continue
working with the new/updated
>> node, and the only way to do it is to look for it after these operations.
>>
>> What do you think about this?
>>
>> ./alex
>> --
>> .w( the_mindstorm )p.
>>
>
>
>
>
>
>
>
!DSPAM:43ba77e0129782181220919!
