[jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1033) Clarify usage of DummyTransactionManager in 2.0

Manik Surtani (JIRA) jira-events at lists.jboss.org
Thu Apr 26 08:04:30 EDT 2007


     [ http://jira.jboss.com/jira/browse/JBCACHE-1033?page=all ]

Manik Surtani updated JBCACHE-1033:
-----------------------------------

    Fix Version/s: 2.0.0.CR2
                   2.0.0.GA
      Description: 
Node.put(Map map, boolean erase) was removed in 2.0. Users wishing to emulate the replace-all behavior (e.g. put(map, true)) in 2.0 must now use a TransactionManager to do first the clear then the putAll().

The docs suggest for stand-alone installs to use the DummyTXMan, but also say it's not production ready.

I would suggest renaming DummyTXM to NonDurableTXM and clarifying the documents.

It'd be also wise to have a section on migration, e.g. "What happened to XXX?"

  was:

Node.put(Map map, boolean erase) was removed in 2.0. Users wishing to emulate the replace-all behavior (e.g. put(map, true)) in 2.0 must now use a TransactionManager to do first the clear then the putAll().

The docs suggest for stand-alone installs to use the DummyTXMan, but also say it's not production ready.

I would suggest renaming DummyTXM to NonDurableTXM and clarifying the documents.

It'd be also wise to have a section on migration, e.g. "What happened to XXX?"


> Clarify usage of DummyTransactionManager in 2.0
> -----------------------------------------------
>
>                 Key: JBCACHE-1033
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1033
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Elias Ross
>         Assigned To: Manik Surtani
>             Fix For: 2.0.0.GA, 2.0.0.CR2
>
>
> Node.put(Map map, boolean erase) was removed in 2.0. Users wishing to emulate the replace-all behavior (e.g. put(map, true)) in 2.0 must now use a TransactionManager to do first the clear then the putAll().
> The docs suggest for stand-alone installs to use the DummyTXMan, but also say it's not production ready.
> I would suggest renaming DummyTXM to NonDurableTXM and clarifying the documents.
> It'd be also wise to have a section on migration, e.g. "What happened to XXX?"

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list