cayenne-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "WONDER" <>
Subject Re: [solved] Re: Cayenne.xml not found.
Date Tue, 04 Apr 2006 14:39:12 GMT
I agree with you, I am trying to do many stuff at once.
And this should work. particularly that the application using own framework
runs in Eclipse and on WO Server.

I belive 50% the problems on deploying an application is "something not

about  appName.jar, Yes I am sure, I see the path in the output.

about :"c:/myPath/Cayenne.xml"
Yes you are also here write, i dont want to. But for testing is prity great
idea, dont you think?
As a last solution, you create the same path on your server also, and it
"should" work.


----- Original Message ----- 
From: "Mike Kienenberger" <>
To: <>
Sent: Tuesday, April 04, 2006 4:20 PM
Subject: Re: [solved] Re: Cayenne.xml not found.

On 4/4/06, WONDER <> wrote:
> The application is too complicated.
> I am prity sure adding the XMLs to the jar file "should" work, but it does
> not.
> I use custom framework and the class which call the Cayenne.xml is there.

I think part of the problem is that you're trying to do too many things at
If I recall, you not only want to integrate Cayenne with WebObjects,
but you are also trying to  use a package name for all of your xml

I think you'd be better off getting Cayenne working with Webobjects in
the default configuration first, then trying to add the packaging of
your xml files.

I posted how you'd get the packaging to work in a previous message.
Dropping your xml files in your src directory should be all that's
needed to get them into your class package, provided your build script
then copies them over into your classes directory or jar file.

Are you sure that your appName.jar is read out of Resources/Java?   In
my WO 5.2 project, I have a WEB-INF/classes directory that I use
instead of a jar file.   Looking at my Resources/Java/*.jar file, I
see that it's empty.

You don't want to use something like this "c:/myPath/Cayenne.xml"
because it won't work when you go to deploy your application on an
application server.

View raw message