[infinispan-issues] [JBoss JIRA] (ISPN-1907) Enhance to bubble up exceptions that occur during instantiation/wiring of cache loader defined in xml

[Michael Mogley (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678091#comment-12678091 ] 

Michael Mogley commented on ISPN-1907:
--------------------------------------

Yes, once I fixed the property method in the cache-loader implementation, it was successfully instantiated, wired up, and started.
                
> Enhance to bubble up exceptions that occur during instantiation/wiring of cache loader defined in xml
> -----------------------------------------------------------------------------------------------------
>
>                 Key: ISPN-1907
>                 URL: https://issues.jboss.org/browse/ISPN-1907
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Configuration
>    Affects Versions: 5.1.2.FINAL
>         Environment: Windows XP SP3, Oracle JDK 6 patch 31
>            Reporter: Michael Mogley
>            Assignee: Galder Zamarreño
>              Labels: spring
>             Fix For: 5.1.3.CR1, 5.1.3.FINAL
>
>
> When using the SpringEmbeddedCacheManagerFactoryBean, any exception that occurs when attempting to instantiate a CacheStore implementation does not bubble up to the log, even with full error logging turned on. A specific failure case is inadvertently defining the CacheStore implementation property setter method with 'private' scope. Being able to see the error in the log would allow for much quicker diagnosis and resolution of the underlying issue in the implementation. Right now, the only way to find such an issue - other than to simply have it jump out at you in the CacheStore implementation code - is to tediously step through the unmarshalling process in the Infinispan source itself.
> The log is similarly silent about an incorrect setting of the CacheStore class name.

--
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