RE: [Xdoclet-user] Data Object vs Value Object

[Hicks, James]

Title: Message

Are you using container managed relationships ( 1-n or n-n )?  This seems to cause errors with the version i have.  I will get a new CVS version tonight and see what happens.  James Hicks C.A.D.G. - Application Developer BERRYDirect Email: [EMAIL PROTECTED] Phone: 936.462.4655 Fax: 936.462.4655 Pager: 936.568.4296 I-Pager: [EMAIL PROTECTED] -----Original Message----- From: Steve Knight [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 11, 2002 7:34 AM To: [EMAIL PROTECTED] Subject: Re: [Xdoclet-user] Data Object vs Value Object James, What sort of patches are you working on for Value Objects? As Marcus said, Value Objects currently DO work with CMP 2.0, as I am also using them in my own CMP 2.0 project.  There are still a few small bugs I think, and maybe some improvements could be made.  But what exactly are you working on?   Thanks,   Steve   ----- Original Message ----- From: Hicks, James To: JD Brennan ; [EMAIL PROTECTED] Sent: Wednesday, April 10, 2002 8:26 PM Subject: RE: [Xdoclet-user] Data Object vs Value Object Ive heard the concept called all 3: Value Object, Data Object, and Data Transfer Object.  I believe Value Object best describes the concept.  Value Object is used for moving data between remote clients and the server.  It takes a copy of the values on the server and sends them to the client.  You get just the values, not a reference.   If you are working with CMP 2.0, valueobject subtask in XDoclet will not work.  I am currently working on a patch for this, which hopefully, if everything goes right, will be finished this coming weekend.    James Hicks C.A.D.G. - Application Developer BERRYDirect Email: [EMAIL PROTECTED] Phone: 936.462.4655 Fax: 936.462.4655 Pager: 936.568.4296 I-Pager: [EMAIL PROTECTED] -----Original Message----- From: JD Brennan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 10, 2002 2:02 PM To: [EMAIL PROTECTED] Subject: RE: [Xdoclet-user] Data Object vs Value Object Thanks.  That makes sense.  Martin Fowler uses the name Data Transfer Object for the Sun pattern Value Object.   Has the Java community settled on the name Value Object, or might the name Data Transfer Object be more appropriate for XDoclet?   I don't really care one way or the other, I'm just trying to stick my finger in the air to see which way the wind is blowing.  ;-)   Tx! JD   -----Original Message----- From: Vincent Harcq [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 09, 2002 10:07 PM To: 'JD Brennan'; [EMAIL PROTECTED] Subject: RE: [Xdoclet-user] Data Object vs Value Object DO is the same concept as VO. VO will replace DO in the future.  More powerful.   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of JD Brennan Sent: mercredi 10 avril 2002 2:39 To: '[EMAIL PROTECTED]' Subject: [Xdoclet-user] Data Object vs Value Object What's difference between data object and value object in XDoclet? I've found documentation for the Value Object pattern (http://java.sun.com/blueprints/patterns/j2ee_patterns/value_object/index.html) and for the Data Access Object pattern (http://java.sun.com/blueprints/patterns/j2ee_patterns/data_access_object/) But I can't find a definition of the "Data Object" pattern. It seems that in XDoclet the <dao> subtask is different from the <dataobject> subtask, so am I correct in assuming the dao and dataobject don't have anything to do with each other in XDoclet? Thanks for any enlightenment! JD "The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged 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 received this in error, please contact the sender and delete the material from all computers." "The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged 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 received this in error, please contact the sender and delete the material from all computers."