hummmm.... fixing this bug about the toString, I of course find myself opening yet another multiple layer russian doll... well this one might not be that deep since I had solved it in jboss1.0. There is one particular problem that I hadn't completely solved is the hashing of the proxy. In jboss1.0 I returned the hash for the database pk in case of entity and the ejbossPK (proprietary build) in case of session, I don't have the later here. Do we want to expose other hashes? particularly in case someone decides to override the hashcode of the beans itself, do we want to propagate it?. It that something you would find of value... it is a fairly more complex construct than just returning blindly this.hashcode from the proxy (or id) but I guess it can be done. Then maps of these things would actually "see" the proxies as identical and stuff... might be useful, I don't know. Smoking crack? marc ________________________ Marc Fleury Chief Technology Officer Telkel, Inc. ________________________
