[
https://issues.apache.org/jira/browse/POOL-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506659
]
Phil Steitz commented on POOL-98:
---------------------------------
I don't think we want to expose the _pool, since this is actually a linked list
of idle objects, so exposing it is not that useful and would really tie GOP to
the current internal implementation if we allowed subclasses to depend on it.
Other than the current counters numActive, numIdle, and the pool properties,
what would be most useful for management?
> Make GenericObjectPool better extensible
> ----------------------------------------
>
> Key: POOL-98
> URL: https://issues.apache.org/jira/browse/POOL-98
> Project: Commons Pool
> Issue Type: Improvement
> Affects Versions: 1.3
> Reporter: Henning Schmiedehausen
> Priority: Minor
>
> The current implementation of GenericObjectPool encapsulates the _pool
> object and there is no way to get it directly, which makes some things
> like JMX pool monitoring a bit awkward.
> Would it be possible to either make _pool protected or add a method
> protected Collection getInternalPool() {
> return _pool;
> }
> or something like that to the GenericObjectPool implementation (and
> probably others, but that is the one that bites me most... :-) )
> This would make extending the GenericObjectPool much easier.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
