[infinispan-issues] [JBoss JIRA] (ISPN-1675) InstantiationExceptions using new Configuration API

Pete Muir (Updated) (JIRA) jira-events at lists.jboss.org
Mon Jan 9 08:15:09 EST 2012


     [ https://issues.jboss.org/browse/ISPN-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Muir updated ISPN-1675:
----------------------------


Until we upgrade Infinispan to use the new API natively, which will be for 5.2.0, I will add a note to the effect that the instance will not be preserved, and you need to provide a no-args constructor.
                
> InstantiationExceptions using new Configuration API
> ---------------------------------------------------
>
>                 Key: ISPN-1675
>                 URL: https://issues.jboss.org/browse/ISPN-1675
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Configuration
>    Affects Versions: 5.1.0.CR2
>            Reporter: Paul Ferraro
>            Assignee: Pete Muir
>             Fix For: 5.1.0.CR3
>
>
> The following code fragments will cause an InstantiationException:
> new DefaultCacheManager(new GlobalConfigurationBuilder().transport().transport(new JGroupsTransport(channel)).build()).getCache();
> new DefaultCacheManager(new GlobalConfigurationBuilder().asyncTransportExecutor().factory(new CustomExecutorFactory(executor)).build()).getCache();
> Even though the new configuration API accepts object instances for these configuration properties, they are expected to have no-arg constructors (since the old configuration API relied on this mechanism), hence the InstantiationException.

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

        


More information about the infinispan-issues mailing list