comment on

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.

In reply to Re: Quite confuse about using Class::DBI to implement Data Access Objects and Value Objects Design Patterns by izut
in thread Quite confuse about using Class::DBI to implement Data Access Objects and Value Objects Design Patterns by monsieur_champs

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Just another Perl shrine
	PerlMonks