OK, so the question is “how”.
(I spent about 45min hacking different combinations and none worked. All I
could get working is depositing all the config files in the top level
WEB-INF/classes dir. I am sure I am missing something but the previous two
solutions stopped working with 4.0)
>
> On Jul 5, 2015, at 8:51 PM, Joe Baldwin wrote:
>
>>
>> "configuration-location" init parameter.”
>
>
> This was mentioned in the docs. Is this not good practice?
>
> I would *prefer* to put them in a separate directory under “classes”. Is
> there a better way to do this - in your experi
> IIRC the last time this changed was in 3.1. 4.0 and 3.1 should be the same in
> this respect.
I wrote my code a couple of versions back. This is the second change is
location for me so far. (1. dir defined in web.xml, and then 2. in the top
level WEB-INF/lib dir)
> "configuration-location
I guess these definitions change a bit given the DBMS.
Some discussions claim that Catalog is like Database, while Schema is like
Table. That seems to fit with the Modeler’s implementation (MySQL), so that
when the sql is generated it looks like
Catalog.Schema
MySQL Workbench has a
Yep, absolutely right.
> On Jul 5, 2015, at 8:27 PM, Joe Baldwin wrote:
>
> Andrus,
>
> in the interim, I did some hacking and found out that I needed
> cayenne-di-4.0.M2.jar
> as well
> cayenne-server-4.0.M2.jar
>
> The error, without the the di jar was that Modules were missing.
IIRC the last time this changed was in 3.1. 4.0 and 3.1 should be the same in
this respect.
All XML file locations are relative to CLASSPATH, regardless of whether you are
using CayenneFilter or not. CayenneFilter simply creates a ServerRuntime with
location parameter, so everything we say abo
Andrus,
in the interim, I did some hacking and found out that I needed
cayenne-di-4.0.M2.jar
as well
cayenne-server-4.0.M2.jar
The error, without the the di jar was that Modules were missing. So, if I
haven’t missed anything, you need server, di, and all the 3rd party jars at a
> On Jul 5, 2015, at 2:44 PM, Joe Baldwin wrote:
>
> What does Cayenne Modeler -> DbEntity Configuration -> Catalog configuration
> field refer to?
>
> (I could find no documentation on this. The Javadocs simply note the name.)
> It appears to pre-append a name to the database-name in the
Yes. Alternatively you can use ServerRuntimeBuilder (especially if you have
various customizations), but ServerRuntime constructor works just as well.
Andrus
> On Jul 4, 2015, at 1:30 PM, Joe Baldwin wrote:
>
> Is this example from (https://cayenne.apache.org/docs/4.0/tutorial/ch05.html
>
While migrating to 4.0, I have found that the config files assoicatated with
the filter cannot be located. It appears that the location rules have changed
again.
This doc
https://cayenne.apache.org/docs/4.0/cayenne-guide/starting-cayenne.html#webapps
says:
"When started by the web c
What does Cayenne Modeler -> DbEntity Configuration -> Catalog configuration
field refer to?
(I could find no documentation on this. The Javadocs simply note the name.)
It appears to pre-append a name to the database-name in the generated SQL.
While migrating to 4.0, I have found that the config files assoicatated with
the filter cannot be located. It appears that the location rules have changed
again.
This doc
https://cayenne.apache.org/docs/4.0/cayenne-guide/starting-cayenne.html#webapps
says:
"When started by the web c
What does Cayenne Modeler -> DbEntity Configuration -> Catalog configuration
field refer to?
(I could find no documentation on this. The Javadocs simply note the name.)
It appears to pre-append a name to the database-name in the generated SQL.
13 matches
Mail list logo
