I am about ready to release the MPool (Managed Pool) stuff, which would provide a nice way to migrate Fortress, etc. As I was refactoring things, I added a really nice feature, and a better approach to instrumenting the pools than we have in Excalibur Pool.
It is the PoolListener. I originally added it to provide feedback to the system when there were unexplained exceptions that should never happen, but were swallowed without a trace. Then I realized it would be a perfectly natural way to handle releasing the resources.
Now you can perform just about any logic at any stage for the pooled objects. It's not recommended to overload it, but it is a nice simple to implement feature that provides a lot of power to the user.
There is no need for library dependency cycles, whatever is needed later can be attached on later. I'll have the library released on Monday (tomorrow is Father's day here in the U.S. so I will be busy with the celebrations).
At that time we can decide if we are going to use the work I have done for Fortress. Again, we have 100% test coverage and better architecture with less code duplication. I have some cleanup in the form of JavaDocs but that will be taken care of shortly.
--
"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."
- Rich Cook
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Apache Excalibur Project -- URL: http://excalibur.apache.org/
