> From: Peter Royal [mailto:[EMAIL PROTECTED]] > > There's no harm in keeping it around. People can potentially > shoot themselves > in the foot if they like :)
They *can* use it, but its use should be discouraged. I am not saying it should be completely removed yet. I want it to throw copious warnings though. So much so that people will want to reengineer the component to make it so it isn't required. I have a new default handler that is better. More below. > > I have some components that can be used for a SAX pipeline, > and thus the > components aren't threadsafe. I decided for a factory vs > pooling because the > program only needs one component every 24hrs, since it is > part of an EDI > interface. A pool seemed like a waste of resources. In Fortress, it can be changed to PerThreadComponentHandler very easily. The PerThreadComponentHandler uses lazy initialization, but ensures there is no more than one instance of the component per thread of execution. If your thread that used the component dies, the component will be removed from use. If there are no more requests, there are no more instances. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
