What do you mean? This is often our case. I mean, we often have composite
value objects: one that contains another, which contains another. Are there
any issues with such design?
Example:
public class OrderVO implements Serializable {
/** Order lines */
private LinesVO[] orderLines; //Eclipse will do the rest
//Other attributes....
}
public class LinesVO implements Serializable {
/** Line Items */
private LineItemsVO[] lineItems;//Eclipse will do the rest
//Other attributes...
}
public class LineItemsVO implements Serializable {
/** Item code */
private int id;//Eclipse will do the rest
}
And so on.
>
ActionForms aren't perfect. However, what they buy you in terms of
everything else, usually make them well worth it. Where they tend to be a
bit of a pain is in trying to model complex object models in one form.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
