Steve Knight
2002-04-11 19:00:16 UTC
Well, I have around 17 tables in my project (all beans generated by
Middlegen - Thank you!) and as I go along I am uncovering bugs, which I have
posted here, and most have been patched by Marcus or Vincent.
I am using these relationships, so far:
1<->1
1<->n
1<--n
The bi-directional relationships are currently a problem because you can get
circular references. I got around this by excluding the cmr field on one
end of the relationship. Of course, then you lose the ability to navigate
the relation from that end!
Steve
----- Original Message -----
From: <***@netcom.no>
To: "Hicks, James" <***@LMBerry.com>
Cc: "Marcus Brito" <***@animegaiden.com.br>; "Lista XDoclet-User"
<xdoclet-***@lists.sourceforge.net>
Sent: Thursday, April 11, 2002 2:01 PM
Subject: Re: RE: [Xdoclet-user] Data Object vs Value Object
Just a suggestion for testing and debugging this value baby: Use
Middlegen. With 8 related tables you'll get 7 relationships, right?
That's enough to cover all combinations of cardinality and
directionality:
1-->1
1-->n
m-->m
m<->m
It would be error prone and painful to code all these test classes
(which you do need indeed) by hand. Make your life easier and your code
better.
You'll have to edit the entity-cmp.j template in Middlegen in order to
make it generate value objects (isn't value _classes_ more correct?).
Middlegen/XDoclet will stress the value object to the max with all
these combinations. There should be some JUnit tests to test it too.
This stuff is too complex for ad hoc testing.
(This would go to Vincent too if I had his email handy, but I don't.
He'll read it anyway).
Regards,
Aslak
----- Original Message -----
From: "Hicks, James" <***@LMBerry.com>
Date: Thursday, April 11, 2002 5:34 pm
Subject: RE: [Xdoclet-user] Data Object vs Value Object
Middlegen - Thank you!) and as I go along I am uncovering bugs, which I have
posted here, and most have been patched by Marcus or Vincent.
I am using these relationships, so far:
1<->1
1<->n
1<--n
The bi-directional relationships are currently a problem because you can get
circular references. I got around this by excluding the cmr field on one
end of the relationship. Of course, then you lose the ability to navigate
the relation from that end!
Steve
----- Original Message -----
From: <***@netcom.no>
To: "Hicks, James" <***@LMBerry.com>
Cc: "Marcus Brito" <***@animegaiden.com.br>; "Lista XDoclet-User"
<xdoclet-***@lists.sourceforge.net>
Sent: Thursday, April 11, 2002 2:01 PM
Subject: Re: RE: [Xdoclet-user] Data Object vs Value Object
Just a suggestion for testing and debugging this value baby: Use
Middlegen. With 8 related tables you'll get 7 relationships, right?
That's enough to cover all combinations of cardinality and
directionality:
1-->1
1-->n
m-->m
m<->m
It would be error prone and painful to code all these test classes
(which you do need indeed) by hand. Make your life easier and your code
better.
You'll have to edit the entity-cmp.j template in Middlegen in order to
make it generate value objects (isn't value _classes_ more correct?).
Middlegen/XDoclet will stress the value object to the max with all
these combinations. There should be some JUnit tests to test it too.
This stuff is too complex for ad hoc testing.
(This would go to Vincent too if I had his email handy, but I don't.
He'll read it anyway).
Regards,
Aslak
----- Original Message -----
From: "Hicks, James" <***@LMBerry.com>
Date: Thursday, April 11, 2002 5:34 pm
Subject: RE: [Xdoclet-user] Data Object vs Value Object
I was unaware that anyone was fixing it to work with CMP2. The
last i heard
was that no special work was going to be performed to make it work
withcmp2. I have a CVS snapshot from about 2 weeks ago.
Here is one build setup I use that causes errors with the version of
- bean class has 1-n relationship with another bean (CMR)
- the other bean is already built and packaged.
- xdoclet generates cmp implementation for bean, local home and
local object
interfaces
- the bean class declares the getValueObject and setValueObject
methods as
abstract.
- xdoclet generates the value object for the bean. it includes the
valueobjects for the 1-n relationship
- when xdoclet goes to generate the cmp implementation with get
and set
methods, it croaks. Since it has been a week since I worked with
it, i
don't remember the exact error message. But the error is caused
when it
trys to write the update*, add*, and remove methods in the bean
for the
relationship.
When i get home tonight, i will run it and email the stack trace.
I will
also get the latest CVS and try it.
James Hicks
C.A.D.G. - Application Developer
BERRYDirect
Phone: 936.462.4655
Fax: 936.462.4655
Pager: 936.568.4296
-----Original Message-----
Sent: Wednesday, April 10, 2002 9:54 PM
To: Lista XDoclet-User
Subject: RE: [Xdoclet-user] Data Object vs Value Object
recently and
I think that the current state is OK for CMP2. If you find
anything that
doesn't work, file a bug on sourceforge.net and someone (me or
vincent,probably) should take care of it.
I'm even using the VO task in my own project (w/ CMP2).
--
Anime Gaiden - De fãs para fãs, sempre.
http://www.animegaiden.com.br
"The information transmitted is intended only for the person or
entity to
which it is addressed and may contain confidential, proprietary,
and/orprivileged material. Any review, retransmission,
dissemination, or other use
of, or taking of, any action in reliance upon this information by
persons or
entities other than the intended recipient is prohibited. If you
receivedthis in error, please contact the sender and delete the
material from all
computers."
_______________________________________________
Xdoclet-user mailing list
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
last i heard
was that no special work was going to be performed to make it work
withcmp2. I have a CVS snapshot from about 2 weeks ago.
Here is one build setup I use that causes errors with the version of
- bean class has 1-n relationship with another bean (CMR)
- the other bean is already built and packaged.
- xdoclet generates cmp implementation for bean, local home and
local object
interfaces
- the bean class declares the getValueObject and setValueObject
methods as
abstract.
- xdoclet generates the value object for the bean. it includes the
valueobjects for the 1-n relationship
- when xdoclet goes to generate the cmp implementation with get
and set
methods, it croaks. Since it has been a week since I worked with
it, i
don't remember the exact error message. But the error is caused
when it
trys to write the update*, add*, and remove methods in the bean
for the
relationship.
When i get home tonight, i will run it and email the stack trace.
I will
also get the latest CVS and try it.
James Hicks
C.A.D.G. - Application Developer
BERRYDirect
Phone: 936.462.4655
Fax: 936.462.4655
Pager: 936.568.4296
-----Original Message-----
Sent: Wednesday, April 10, 2002 9:54 PM
To: Lista XDoclet-User
Subject: RE: [Xdoclet-user] Data Object vs Value Object
If you are working with CMP 2.0, valueobject subtask in XDoclet
will notwork. I am currently working on a patch for this, which
hopefully, ifeverything goes right, will be finished this coming weekend.
Hey, it DOES work. I've put some effort into Value Objectsrecently and
I think that the current state is OK for CMP2. If you find
anything that
doesn't work, file a bug on sourceforge.net and someone (me or
vincent,probably) should take care of it.
I'm even using the VO task in my own project (w/ CMP2).
--
Anime Gaiden - De fãs para fãs, sempre.
http://www.animegaiden.com.br
"The information transmitted is intended only for the person or
entity to
which it is addressed and may contain confidential, proprietary,
and/orprivileged material. Any review, retransmission,
dissemination, or other use
of, or taking of, any action in reliance upon this information by
persons or
entities other than the intended recipient is prohibited. If you
receivedthis in error, please contact the sender and delete the
material from all
computers."
_______________________________________________
Xdoclet-user mailing list
https://lists.sourceforge.net/lists/listinfo/xdoclet-user