Hi Brent,
I see no reason why setters can't exist for AnyNode. I guess Arnaud just
added them to the constructor for use during unmarshalling since we
don't change the value, no additional setters were needed.
So it was probably simply that they were not needed at the time, I don't
think there was any other reason.
--Keith
> Brent Picasso wrote:
>
> Keith / All
>
> I was investigating the use of AnyNode to represent arbitrary XML
> data (like "user defined fields" and etc.) as part of my mapping. I
> noticed that interface for AnyNode is not mutable- there are no
> setters- especially for the node values.
>
> What are the thoughts on this? Was this intentional, or could the
> interface be enhanced to allow the node values to be changed?
>
> Thanks,
> Brent
>
>
> ---------------------------------------------------------------
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [EMAIL PROTECTED] with a subject of:
> unsubscribe castor-dev
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
