Hi,
After a quick look, WebObject looks like a GUI helper for Webwork/Struts
up to Database through EJB or not. Am I far from the truth ?
...
And these are really the product I use at Web Tier (Struts in fact
mainly for its JSP Tag library, I have to investigate the more simple
(so productive?) way to use Action and Form of Webwork)
I am not sure I want to go that far...
I mean there is no big consensus on how client talks to ejbs, Value
Object is here only one possible solution. So I want to go the further
possible with that solution but remains simple. For me simple means
ValueObject have to be JavaBeans, not more.
Look, there is now aggregation or composition implemented, I think this
is needed, accepted for everybody...
A step further is to keep in the VO what properties the client has
changed to not call setter on ejb property if it has not been updated
(for a getAttr()/setAttr() have also a isModifiedAttr())
Etc...etc...etc...
For 1-n relationships (well I think about that now) it gets more
complex.
I think I will do sth like this (OrderValue having a Collection of
OrderLineValue)
public OrderLineValue[] getOrderLines()
public void addOrderLine()
public void removeOrderLine()
public void updateOrderLine()
I think that is the NonMutableArray of WebObject ;-)
So I can keep track of what OrderLines have changed in OrderValue
I am frigthened to give
public Collection getOrderLines()
because then I can not track the change in the List from OrderValue (and
need a special List impl with introspector....pfff... Well that is what
I am doing today)
Still my solution does not avoid a client to do
getOrderLines()[7].set...
Pfff...
What about public OrderLineValue[] getNotMutableOrderLines() to "tell"
the client and clone() the entries to warn the user..
I took the hot potatoes in my hands, I think I have to cold it myself
now ;)
All this because Java is wo weak on Collection package... Anyway back to
thinking...
Vincent
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On Behalf
> Of Ara Abrahamian
> Sent: samedi 9 février 2002 21:20
> To: 'Vincent Harcq'; [EMAIL PROTECTED]
> Subject: RE: [Xdoclet-devel] CVS update:
> xdoclet/core/resources/xdoclet/ejb
>
>
> > Log Message:
> > True agregation in value objects.
> > That means that if AccountBean have a Customer link, it
> does not have
> > And AccountValue wants CustomerNormalValue in it Then
> AccountBean does
> > not need CustomerNormalValue at all, xdoclet
> will do
> > that for you.
> > Isn't it kind ?
>
> Definitely. Keep us the good work :o)
>
> Anyway, I think you'll enjoy reading about Apple Webobjects's
> eocontrol/eodistribution packages. WO is great for fat client
> apps, unlike J2EE. Look how it handles the issue of
> distribution of objects/valueobjects. You'll get ideas to
> improve valueobject mechanism further too.
>
> Cheers,
> Ara.
>
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
>
> _______________________________________________
> Xdoclet-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
>
>
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
