You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Sebb (Created) (JIRA)" <ji...@apache.org> on 2011/12/14 15:23:31 UTC

[jira] [Created] (POOL-201) Classes Generic[Keyed]ObjectPoolConfig are generic - but why?

Classes Generic[Keyed]ObjectPoolConfig are generic - but why?
-------------------------------------------------------------

                 Key: POOL-201
                 URL: https://issues.apache.org/jira/browse/POOL-201
             Project: Commons Pool
          Issue Type: Bug
            Reporter: Sebb


The classes Generic[KeyedObject]PoolConfig are generic - but why?

They don't use the parameterised types anywhere as far as I can tell.

Unless I'm missing something, I don't think the parameterisation provides any useful compile-time checking; it just make the ctors harder to read ...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (POOL-201) Classes Generic[Keyed]ObjectPoolConfig are generic - but why?

Posted by "Mark Thomas (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/POOL-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13169618#comment-13169618 ] 

Mark Thomas commented on POOL-201:
----------------------------------

It is a left-over from when the factory was part of the config class. I'll remove the generics.
                
> Classes Generic[Keyed]ObjectPoolConfig are generic - but why?
> -------------------------------------------------------------
>
>                 Key: POOL-201
>                 URL: https://issues.apache.org/jira/browse/POOL-201
>             Project: Commons Pool
>          Issue Type: Bug
>            Reporter: Sebb
>
> The classes Generic[KeyedObject]PoolConfig are generic - but why?
> They don't use the parameterised types anywhere as far as I can tell.
> Unless I'm missing something, I don't think the parameterisation provides any useful compile-time checking; it just make the ctors harder to read ...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (POOL-201) Classes Generic[Keyed]ObjectPoolConfig are generic - but why?

Posted by "Mark Thomas (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/POOL-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Thomas resolved POOL-201.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0
    
> Classes Generic[Keyed]ObjectPoolConfig are generic - but why?
> -------------------------------------------------------------
>
>                 Key: POOL-201
>                 URL: https://issues.apache.org/jira/browse/POOL-201
>             Project: Commons Pool
>          Issue Type: Bug
>            Reporter: Sebb
>             Fix For: 2.0
>
>
> The classes Generic[KeyedObject]PoolConfig are generic - but why?
> They don't use the parameterised types anywhere as far as I can tell.
> Unless I'm missing something, I don't think the parameterisation provides any useful compile-time checking; it just make the ctors harder to read ...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira