> How can you put *anything* into the remote?
In exactly the way you mention. That's what I meant - sorry
if it was unclear. The remote method becomes a call to a
bean method containing validation logic which optionally
calls a setter. This is in contrast to the no-brainer
approach of having the remote simply contain the
getter/setter methods and the bean pass-through these calls
directly.
> Whoa there. Interceptors have nothing to do with it.
> There is nothing which
> requires that the CMP/CMR getter/setters be business
> methods, so you can
> have validation, *exactly* the same as EJB 1.1, without
> interceptors, value
> objects, or any other buzzwords. See my earlier post.
Yes of course you're right. It's a required mindset change
which I haven't completed yet (still using 1.1 in 'obvious
mode').
I believe the mention of interceptors was to do with
automated value-object generation, nothing more.
c
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
