Hmm.. curiouser and curiouser:
I'm reorganising the entity setup, and now I get:
org.apache.cayenne.CayenneRuntimeException: [v.3.1M4-SNAPSHOT Dec 11 2011
10:30:28] ObjAttribute 'number' does not have a corresponding DbAttribute
My setup, below, links the two:
id, in this case, is the magic "num
What am I missing: In
DataDomainInsertBucket#createPermIds
the returned node is null in:
DataNode node = parent.getDomain().lookupDataNode(entity.getDataMap());
Clearly I'm not doing something in my set-up.
On 11 Dec 2011 at 21:05, Andrus Adamchik wrote:
> Great to hear there a
Great to hear there a workaround. Object structure is a pretty fundamental
issue, so I was afraid we may get stuck here.
Cheers,
Andrus
On Dec 11, 2011, at 8:49 PM, Kevin Meyer - KMZ wrote:
> On 11 Dec 2011 at 20:28, Andrus Adamchik wrote:
>
>>
>> On Dec 11, 2011, at 7:00 PM, Kevin Meyer - K
On 11 Dec 2011 at 20:28, Andrus Adamchik wrote:
>
> On Dec 11, 2011, at 7:00 PM, Kevin Meyer - KMZ wrote:
>
> > I wish it were this simple. But the problem lies in
> > DataContext#newObject(String entityName)
> > once it has created an instance of my POJO, it type casts it to
> > Persistent
On Dec 11, 2011, at 7:00 PM, Kevin Meyer - KMZ wrote:
> I wish it were this simple. But the problem lies in
> DataContext#newObject(String entityName)
> once it has created an instance of my POJO, it type casts it to
> Persistent:
>object = (Persistent) descriptor.createObject(
You're right about the max # of concurrent users, but the max # of required
connections is usually < the max # of concurrent users. Cayenne only needs a
connection to query the db or to commit to the db. Outside of those operations,
connections are returned to the pool, so you can usually get by
I just had a look at the Modeler and at the DomainNode's JDBC Configuration
(in the Main tab). I saw that 'Max Connections' was set to '1'. So perhaps
I wasn't giving Cayenne much to play with in terms of connection pooling! I
have now set it to '2'. (I imagine the default was a bit higher than the
Hm. Cayenne is usually pretty good about managing the connection pooling for
you.
How many concurrent connections is your mysql db configured to allow?
Robert
On Dec 11, 2011, at 12/119:58 PM , Chris Murphy (www.strandz.org) wrote:
> Thanks Robert,
>
> That was the answer. The memory leak disa
By the way, I'm using Cayenne 3.1M4-SNAPSHOT.
> I don't really know what you're doing, but what about something like this:
>
> class POJO {
> CayenneDataObject delegate;
>
> public POJO() {
> }
>
> public setDelegate(CayenneDataObject cdo) {
> this.delegate = cdo;
>
Thanks Robert,
That was the answer. The memory leak disappeared. I now create a
DataContext with 'method scope' that gets gc-ed when the method has
finished. That brought up what must be another problem with my code which
I'm investigating now:
Caused by: org.apache.cayenne.CayenneRuntimeExceptio
I don't really know what you're doing, but what about something like this:
class POJO {
CayenneDataObject delegate;
public POJO() {
}
public setDelegate(CayenneDataObject cdo) {
this.delegate = cdo;
}
// or
public POJO(CayenneDataObject cdo) {
this.del
2011/12/10 Aristedes Maniatis :
> On Sat Dec 10 16:39:50 2011, Andrus Adamchik wrote:
>>
>> Could be a bug (in Derby?). Probably worth opening a bug report at
>> https://issues.apache.org/jira/browse/CAY ... Also would be helpful if you
>> could take a thread dump when the app is frozen to see what
I'm still having trouble with this. I had to generate again because I
messed it all up trying to get inheritance to work the way I want.
It takes a VERY long time to generate the ObjEntities. Several hours.
Something must be wrong here somewhere.
Has nobody else experienced this?
As I said befor
Thanks - I've got to the point where Cayenne is trying to instantiate an
instance of one of my pojos, but I've run into a problem...
Cayenne *requires* the pojo to implement the Persisted interface, but
this interface kills the Isis introspector (it detects the XMLSerializer,
which contains a
14 matches
Mail list logo
