Mathias, anything else you would want to assign to me? :-)
Ara.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:legendaryservice@;atlassian.com]
> Sent: Friday, November 08, 2002 9:11 PM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: [JIRA] Assigned: (XDT-145) ejb.persist
Hi all,
one more thought after the chat:
When an entity bean returns "too many" different views (i.e. different VO
classes) of itself, the programmer should consider to move the code out into
the session facade. (The notion of "too many" depends on the project
context).
> In the case where VOs a
hey all,
just had a chat with Matthias about this, and hopefully the following gives
a concise summary:
There are two main variables that affect the decision as to where VOs should
be created:
- team structure
- use case variety
team structure - in team structures where one developer is
sure - I'm colebatchd, what's your yahoo id?
- Original Message -
From: "Matthias Bohlen" <[EMAIL PROTECTED]>
To: "'Dmitri Colebatch'" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Sunday, November 10, 2002 1:39 AM
Subject: RE: [Xdoclet-devel] VOs are bound to use cases!
> Hi Dmitri,
Hi Dmitri,
this seems to be an interesting subject - however, my defunct brain could
not get the point from your explanation :-).
Maybe, we should switch from Email to a medium with more bandwidth. Do you
support Yahoo Messenger so that we can have an audio chat? Maybe, others
want to join in?
C
Hi smart folks,
whew, fantastic! So many different points of view in this discussion! I love
to disagree with somebody because this somebody and I learn very much.
You (the other "somebodies") make different assumptions about projects
(that's perfectly OK, because there is no single J2EE project
Even better, you can easily tie your VO's with the Swing components if you
are using a good MVC architecture, like the one provided in the Scope
framework (http://scope.sf.net). Just tell which property of the VO you want
to display in your Swing component, and here you go.
Ludovic
- Original
