On Tue, Sep 2, 2008 at 4:23 AM, Wade Chandler <[EMAIL PROTECTED]> wrote: > What I'm getting at is those TOs can hold some logic used on both sides in > the situations where needed, and that logic itself is not going to be > serialized for instances held within a JavaSpace. The logic I'm talking about > is of course state mantainence as it relates to properties or JavaBean > specifications. The only thing being marshaled are the fields not the > methods. Just being able to encapsulate some things means you can control > state and double duty those objects a bit better...more protection even in > logic you intend to always be secure. And, that logic will not be marshaled, > just the state or fields.
AFAIK, you can serialized anything into the JavaSpace. The public field requirement is only for what can be used to look up those instances later. The rest of this discussion is mostly about programming patterns, and every developer thinks he knows better.... ;o) Cheers Niclas
