Andrus,
I don't think that there were to be problems, we actually are working with
click 1.4 and cayenne
3.0, but we are having trouble with the deserialization process.
I must aggregate that we aren't very experienced with java, and we would prefer
the framework as it
comes.
Thank you again
H
Any reason why you can't use Cayenne 3.0 with Click? (I know it is
tested with 2.0, but I'd imagine it will happily work with 3.0 as
well...or not?)
Andrus
On May 5, 2008, at 3:36 PM, Hans Poo wrote:
Hi,
I'm using click 1.4 with cayenne 2.04.
The whole problem is this: when i begun worki
Hi,
I'm using click 1.4 with cayenne 2.04.
The whole problem is this: when i begun working with click an cayenne, i
installed/copy the
libraries manually, and used cayenne 3.0.
Latter on, i wanted to use the standard click 1.4 pack (with cayenne 2.04
included), but i was
forced to keep cayenne
Umm, sorry you already said that you don't have doubly mapped class...
So what environment are you using for deployment? I am wondering if
there is some special ClassLoader setup involved.
Andrus
On May 5, 2008, at 11:28 AM, Andrus Adamchik wrote:
Hi Hans,
This may be a genuine error (i.e
Hi Hans,
This may be a genuine error (i.e. you do have two entities that are
mapped to the same Java class). Although the fact that it goes away in
3.0 makes me wonder if there is a bug in 2.0.4 EntityResolver. In 3.0
it is much more robust to various cross-ClassLoader and arbitrary
namin
