Re: Quite confuse about using Class::DBI to implement Data Access Objects and Value Objects Design Patterns

VOs are mostly used in J2EE applications which uses EJBs, IMHO. It's cheaper transfer a Value Object in place of an EJB object itself, in distributed applications.

I don't see the need to implement VOs within Class::DBI, unless you are using SOAP and want to return the representation of your Class::DBI implementation. Another point I see is you can't think in Java when programming in another languages.

Tell your architect to think in Perl when programming in Perl, think in Java when programming in Java (I can't think in Java anymore, that's the reason I program in Perl ;).

Igor S. Lopes - izut
surrender to perl. your code, your rules.

Comment on Re: Quite confuse about using Class::DBI to implement Data Access Objects and Value Objects Design Patterns

Replies are listed 'Best First'.
Re^2: Quite confuse about using Class::DBI to implement Data Access Objects and Value Objects Design Patterns by monsieur_champs (Curate) on Aug 10, 2005 at 22:00 UTC
No, thanks. It's cheaper to me keep the DAO and the VO roles in the same object. I'll use the Class::DBI for both things, and that's fine. Please don't blame my architect. He's learning Perl from scratch, for this single project... it's not his fault. ;-) -- monsieur_champs	[reply]