Concerning value-objects: I make my sessionbean
usecases also available through webservices. Which is
a common design and will become more common when
JSR 109 is implemented in J2EE 1.4. Then my value-
objects that I use to exchange domain-object trees with
the client will become SOAP-serialized. This will not
work when the value-objects implement any CM
relations. (I think it's great, by the way, that they DO
support CM relations) The 1-n relations between value-
objects are implemented using methods with a
java.util.Collection as a result value.
But SOAP can not deserialize untyped collections.
Which is logical when you think about it. See the axis-
user mailinglist thread that starts at
This could be fixed by providing, maybe by some switch,
the possibility to generate methods that return arrays of
the specific value-object instead of collections. Adding
and deleting value-object instances to the relation
should then be handled differently ofcourse.
On the xdoclet-user list there was heartfelt support for
this request from David Ward.
Joost de Vries