wiradikusuma wrote:
how did you do that precisely?
i have a User object which has another User as its property. db-load chokes
when called :-(
Two choices: It's possible that while your schema is circular, your
entries do not contain circular references, in which case you can order
the entri
Michael Horwitz wrote:
The other approach we are toying with is bundling all the
configuration into the war upfront, and getting the application to
intelligently detect its environment and configure itself
accordingly.
But if you have sticklers in QA (as you describe), I don't see how they
cou
I have one field as FK too. Everything is ok!
06/12/9, Rene Lavoie <[EMAIL PROTECTED]>:
Thanks for the idea.
Not sure I could do it that way though since one field is a key is a FK
from the parent, so the many-to-one relationship would now be on the
component instead.
- Original Message
Thanks for the idea.
Not sure I could do it that way though since one field is a key is a FK from
the parent, so the many-to-one relationship would now be on the component
instead.
- Original Message -
From: majaa majaa
To: users@appfuse.dev.java.net
Sent: Saturday, December
I have one unique key with 3 fields.
/**
* @hibernate.component unique="true"
*/
in one class and rest for these key in second
Perhaps you can do that only in this way..
majaa
That's an interesting constraint I hadn't thought about. One could follow
the same approach as I describe but instead of rebundling the generated
config settings into the war, they can be generated into a "config"
directory and the startup script can add the config directory to the web
containers
You could use SiteMesh from within a separate application to decorate
the application.
http://raibledesigns.com/page/rd?entry=use_sitemesh_to_decorate_multiple
Either that, or change to using a Velocity decorator that you could
load from a database table.
You could also create some sort of "the
100% agreed! Unfortunately I, like many other I know, work in an environment
where we are strictly forbidden from making any modifications to the binary
after we release to test. The application still has to go to QA, staging and
production environments post test, and a war file is seen by the dep
DNewfield wrote:
>
> Michael Horwitz wrote:
>> As a rule I would try and avoid circular dependencies wherever possible.
>
> whenever I have to do a db-load. (My kludge: alter the tables to
> remove all the foreign key constraints before the db-load, adding those
> constraints back in afterw
