As a background to what Kevin just said, Cayenne itself no longer
attempts to configure Log4J (something it did prior to 3.0). Log4J is
optional and is expected to be configured by the user.
http://cayenne.apache.org/doc/guide-to-30-features.html
(search for "logging" on this page).
And
How are you bootstrapping your log4j configuration? I have something like
the following before creating a DC:
org.apache.log4j.PropertyConfigurator.configure(getClass().getResource("/log
4j.properties"));
--
Kevin
On 2/5/08 11:29 AM, "Alexander Lamb (dev)" <[EMAIL PROTECTED]> wrote:
> Hello
Hello List,
I don't seem to be able to stop Cayenne log all the SQL (3.0M2 or M3).
I have the following in my log4j.properties, but it doesn't seem to be
taken into account!
log4j.category.org.apache.cayenne.access.QueryLogger = WARN
log4j.category.org.apache.cayenne.conf = WARN
log4j.catego
Not sure how you mapped it. As long as you didn't have any aggregate
functions in "derived" entities, you should be fine with implementing
things via ObjEntity inheritance.
Andrus
On Feb 5, 2008, at 1:48 PM, Alexander Lamb (dev) wrote:
Hoho... now I suppose I need to remove the derived DBE
Hoho... now I suppose I need to remove the derived DBEntities and
instead use class inheritance on the object entities side :-)
I ought to be able to do that without changing the code, only the
model ?
Alex
Le 5 févr. 08 à 12:35, Andrus Adamchik a écrit :
Aha... That must be it:
https:/
Aha... That must be it:
https://issues.apache.org/cayenne/browse/CAY-921
Andrus
On Feb 5, 2008, at 1:21 PM, Alexander Lamb (dev) wrote:
More info:
What happened is that we have class hierarchies in our models. With
M2, it works. With M3, it doesn't. What is also curious is that the
inter
More info:
What happened is that we have class hierarchies in our models. With
M2, it works. With M3, it doesn't. What is also curious is that the
interface in the Modeler of M3 does not allow anymore to have a DB
Entity inherit from another DB Entity ?? I guess that is the problem
since
On 05/02/2008, at 10:05 PM, Alexander Lamb (dev) wrote:
But: are the model formats compatible between M2 and M3 ? In other
words, can I continue to work with M3 modeler whatever version M2
or M3 of Cayenne I am using?
Andrus will have the definitive answer with regard to the standard
sc
Ok, I will try.
Maybe the model but I maybe did something stupid: I opened the models
with the M3 modeler then saved them. Still the crash. Then reverted to
M2 (without changing the models). Again a crash which seems to
tell us it is not M3.
But: are the model formats compatible betwe
On Feb 5, 2008, at 11:02 AM, Alexander Lamb (dev) wrote:
Caused by: java.lang.NullPointerException
at
org
.apache
.cayenne
.map.AshwoodEntitySorter.fillInMetadata(AshwoodEntitySorter.java:265)
at
org
.apache
.cayenne
.map.AshwoodEntitySorter._indexSorter(AshwoodEntitySorter.java:98)
Hello List,
I have a crash with M3 that I didn't have with M2. I updated the
models (I have two models), cleaned everything, rebuilt.
Upon first commit I get the following crash.
I am not doing anything special. Just inserting a record then saving.
Several queries worked perfectly well bef
11 matches
Mail list logo
