Thanks Bruno, I fixed it CVS.
--- Bruno Suárez Laffargue
<[EMAIL PROTECTED]> wrote:
-
Hi,
I've seen that my hibernate nevers shows me the sql...
and i have the hibernate.db.showsql=truein
mda/project.properties.
I've done a power search, and found the following
Hi,
I've seen that my hibernate nevers shows me the sql... and i have the hibernate.db.showsql=true
in mda/project.properties.
I've done a power search, and found the following in mda/project.xml line 41:
${hibernate.db.showSql}
I think it shoulb be:
${hibernate.db.showsql}
The s in showSql
Hi,
I had detected that Hibernate does not generate M-N relations correctly.
Particularly, the name of the table is not generated.
Here is an example of the xdoclet generated when a M-N relation exists:
* @hibernate.set
* lazy="true"
* table="${associationEnd.association.tableN
Hello Frederic,
The reason for having only a single
use-case per package is because the cartridge generates a lot of code that is
implicitely derived from the model. This way the user only has to worry about
putting a single use-case in a package, the alternative was modeling _everythin
Hi again,
Was wondering if client side actions (_javascript_)
could not be modelled
with FrontEndEvents going out from a FrontEndView
to the same FrontEndView,
leading to _javascript_ file generation.
Have you ever discussed about this ?
Regards,
Fred.
Hi,
I switched to m3 recently and was trying a few
things when I ran into this.
The error is resolved by effectively
dedicating a package to each use-case.
My question is why should one package be dedicated
to one modeled "process" ?
I mean you could have several processes (eg. "User
Manag
