It's just that I know the general limitation that people have spoken
of in the past - regarding not being able to use custom object
factories uniformly - is a workable approach to solving this problem
at least on a case-by-case basis for most developers.
That way, devs can do it themselves; and it provides us a single
point at which, should someone choose to, we could implement this
modification to the way objects get created when loading objects from
XML which have current DB bindings in that mapping.
It also provides a nice way for that behavior to be optional. :)
On 18 Jul 2005, at 17:47, Ralf Joachim wrote:
Hi Alessandro,
I think such a update-or-create-if-not-available method would be a
good addition to current functions.
I suggest to create a new issue in jira. Write a test case so that
others can reproduce the problem and attach that to the new issue.
We also wouldn't mind if you'll start implementing this function
and contribute that to castor ;-) .
Having said that Gregory's idea to retrieve objects from the
database at unmarshalling by using something like a FieldHandler
also sounds very interesting. As I don't know the XML side well, I
don't know if XML offers something like that or how much work it
would be to implement.
Regards
Ralf
-------------------------------------------------
If you wish to unsubscribe from this list, please
send an empty message to the following address:
[EMAIL PROTECTED]
-------------------------------------------------
