Well, I thought it would be needed when I first saw the endpoint code:-)
I'm using it for the web container: for instance when a web application is deployed, the web container is notified by the listener.
For 1-many relationships it's possible to have the "1" end respond to endpoint-setting and call something on the other end. I don't think this is always the best design, and I don't think it will work for n-m relationships.
david
On Friday, January 2, 2004, at 11:45 PM, Dain Sundstrom wrote:
That may work. What is this actually used for?
-dain
On Jan 3, 2004, at 1:35 AM, David Jencks wrote:
So, we supply the class of the listener instead of the listener? The listener already has a setTarget method, so it really doesn't have much state.
david
On Friday, January 2, 2004, at 10:48 PM, Dain Sundstrom wrote:
I have a problem with this one. To add configuration persistence, I need to be able to restore and recover all state and this listener is simply an object, so there is really no way to store is and reload the listener. There has to be a better way....
-dain
