Someone should write a paper.
Yep :-)
I recall back in my WebObjects/EOF days, instead of using property
setters I always used a generic method with monstrous name of the
Objective C heritage - addObjectToBothSidesOfRelationshipWithKey
and its counterpart
The query certainly looks fishy. I suspect this may be related to
this issue:
http://issues.apache.org/cayenne/browse/CAY-447
Now the question is whether your relationship problem is also related
to that. I guess it would help if you post your DataMap XML subset
containing the 4
Hello,
I have a Web App where Cayenne is deployed using one of the 3 Web
deployment options. I'm wondering if it is possible at the same time to
be able to get a cayenne context from a call that is not related to a
httpServlet request or a HttpSession. So in addition to using it in
Jsp's and
Monstrous? That was my favorite method name! It stated precisely what
it was doing, too. :-) We hardly ever removed anything, so never got
to use removeObjectFromBothSidesOfRelationshipWithKey all that much.
Sigh.
/dev/mrg
PS. For me, it was actually
Monstrous?
In Objective C you'd read a method name with a list of arguments
almost as a sentence in a human language. So it was verbose, but
readable. I was referring to its Java reincarnation - when
concatenated in one word it looks horrible and almost impossible to
type correctly for
I hate to be a curmudgeon, but it sounds like this might go in the
wrong direction, if I understand correctly. You need two sets of
functionality: one that the user sees and transparently updates both
sides of the relationship; the other, internal, that is called by the
external methods
Hello again,
only now have I returned to this issue. Like two months ago I wrote
some code (MyJdbcPkGenerator) but never had time to actually use it =-O
Now I have invested some hours into it, lurking over cayenne source
code trying to find a way to solve my problem. As suggested I have
