[infinispan-issues] [JBoss JIRA] (ISPN-1868) enable() method is missing after async() in "ConfigurationBuilder Programmatic Configuration API"

[Manik Surtani (JIRA)]

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

Manik Surtani resolved ISPN-1868.
---------------------------------

    Resolution: Done

    
> enable() method is missing after async() in "ConfigurationBuilder Programmatic Configuration API"
> -------------------------------------------------------------------------------------------------
>
>                 Key: ISPN-1868
>                 URL: https://issues.jboss.org/browse/ISPN-1868
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Demos and Tutorials
>            Reporter: Christophe Domas
>            Assignee: Manik Surtani
>              Labels: docs, sample_code, user_guide
>             Fix For: 5.1.1.FINAL
>
>
> In 
> doc: https://docs.jboss.org/author/display/ISPN/Configuring+cache+programmatically
> section: "Configuring Infinispan with one or several chained persistent stores is simple too:"
> I think enable() is missing after async() in the following code (with infinispan-5.1.1):
> actual doc:
> {code}
> Configuration config = new ConfigurationBuilder()
>       .loaders()
>         .shared(false).passivation(false).preload(false)
>         .addFileCacheStore().location("/tmp").streamBufferSize(1800).async().threadPoolSize(20).build();
> {code}
> corrected doc:
> {code}
> Configuration config = new ConfigurationBuilder()
>       .loaders()
>         .shared(false).passivation(false).preload(false)
> .addFileCacheStore().location("/tmp").streamBufferSize(1800).async().enable().threadPoolSize(20).build();
> {code}
> I added a comment on the page you can remove (I spent so much time to understand why it didn't works that I've filled a ticket to ask for toString() methods in configuration objects: ISPN-1861)

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