Mike Kienenberger wrote:
Try putting them in the root of your classpath.
It's possible to put them in other locations, but you'd have to have
set up a Configuration instance pointing to the new location.
I don't know where the example expects to find it.
Ok - not sure what the actual issue was,
Try putting them in the root of your classpath.
It's possible to put them in other locations, but you'd have to have
set up a Configuration instance pointing to the new location.
I don't know where the example expects to find it.
On 4/6/07, Reid Thompson <[EMAIL PROTECTED]> wrote:
Reid Thompso
Reid Thompson wrote:
Hi,
trying to get the cayenne webapp tutorial to work using Netbeans.
Getting the error at the end of this email. I have
cayenne-tutorialMap.map.xml cayenne.xml
cayenne-tutorialNode.driver.xml
in WEB-INF -- is this the correct location for these files?
Sorry - inadver
Hi,
trying to get the cayenne webapp tutorial to work using Netbeans.
Getting the error at the end of this email. I have
cayenne-tutorialMap.map.xml cayenne.xml
cayenne-tutorialNode.driver.xml
in WEB-INF -- is this the correct location for these files?
type Exception report
message
desc
Also, this isn't a Cayenne-specific problem, either. I'd so most, if not
all, ORM technologies would have an issue with the DB generating PKs behind
the scenes without the ORM stack knowing the values that were assigned.
Thanks,
/dev/mrg
On 4/6/07, Andrus Adamchik <[EMAIL PROTECTED]> wrote:
On Apr 6, 2007, at 12:53 PM, Jens Mayer wrote:
I'm using cayenne with oracle 9.2.0.3.0
The pk-attributes in my schema are automatically generated by
before-insert-triggers, so cayenne doesn't have to bother
generating any pk. Due to this, I set the PK Generation Strategy
for all DbEntit
Hi,
I'm using cayenne with oracle 9.2.0.3.0
The pk-attributes in my schema are automatically generated by
before-insert-triggers, so cayenne doesn't have to bother generating any
pk. Due to this, I set the PK Generation Strategy for all DbEntities
to "Database-Generated".
And here comes the
Hallo!
I am back with some problems related to the discussion on 27 March. [1]
It is clear that my approach is memory consuming:
"Collecting all nonpersistent objects in a list, which are registered,
to avoid NullPointerException's. And on a commit I will remove them."
Another problem is that re
