Hi all.
Does anyone knows why the cascade element in the various tags
(@hibernate.array, @hibernate.bag, @hibernate.set etc)
does not support all-delete-orphan.
Daniel
--- Daniel Or [EMAIL PROTECTED] wrote:
Hi all.
Does anyone knows why the cascade element in the
various tags
(@hibernate.array, @hibernate.bag, @hibernate.set
etc)
does not support all-delete-orphan.
because it is not implemented yet in xdoclet 1.2.x
( but in 2 )
regards,
Daniel,
is there only an additional value of the cascade attribute
needed or more?
Heiko
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Daniel
OrSent: Tuesday, September 21, 2004 8:58 AMTo:
[EMAIL PROTECTED]Subject: [Xdoclet-user] Hibernate
cascade
Ah, ok
!ATTLIST set cascade
(none|all|save-update|delete|all-delete-orphan|delete-orphan)
#IMPLIED !-- default: none --
I recently ran into a problem using Xdoclet along
with unit tests that I had written. I had a log4j.properties file in / of my
classpath but wasnt receiving any log statements. I eventually realized
the the xdoclet log4j.properties file was being referenced instead of my log4j.properties,
On Tue, 2004-09-21 at 07:57, Daniel Or wrote:
Does anyone knows why the cascade element in the various tags
(@hibernate.array, @hibernate.bag, @hibernate.set etc)
does not support all-delete-orphan.
What version of XDoclet? According to the CVS logs it looks like it's
been in the
Durham David R Jr penned
Or is the real problem that xdoclet somehow ended up in my Junit
classpath (i.e., xdoclet should be in the classpath during code
generation, but not at runtime)?
You only need the XDoclet JARs during code generation, as you say.
That's the easiest solution. Otherwise,
