A while back there was mention of using the DynamicProxy object included in
1.3 ( I checked the archives )
Was the idea to allow the client application to use ONE, simple,
object/interface from which they would be able to
manipulate state as well as invoke behavior.
Then through the use of the DynamicProxy the method would be delegated to
the appropriate Entity or Session bean.
This sounds like a good idea. It would appear to be a more true OO design,
at least from the application
programmers point of view.(Data and behavior together)
It would certainly reduce the amount of objects / interface's / EJB concepts
for
which the application programmer would have to understand and keep track of.
Is this what you guys where talking about ???
Ed Lorenz
[EMAIL PROTECTED]
With no fences, who needs Gates ?
===========================================================================
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".
