There's no doc as such yet. I was thinking of compiling them all in this dev
thread and then put them in a doc while doing the final release...
On Jan 13, 2012, at 3:22 PM, Manik Surtani wrote:
Where is this doc? On Confluence?
Should add that in 5.0, commit and rollback phases were async
Yeah, i'll open it asap.
More stuff, hierarchical changes for RemoteCache and RemoteCacheManager:
http://infinispan.blogspot.com/2011/11/more-locking-improvements-in-infinispan.html
On Jan 13, 2012, at 3:32 PM, Manik Surtani wrote:
Ok. Well, we may as well start the doc and all of us add to
Here it is: https://docs.jboss.org/author/display/ISPN/Upgrading+from+5.0+to+5.1
On Jan 13, 2012, at 4:44 PM, Galder Zamarreño wrote:
Yeah, i'll open it asap.
More stuff, hierarchical changes for RemoteCache and RemoteCacheManager:
On Jan 11, 2012, at 3:25 PM, Sérgio Miguel Fernandes wrote:
On 10 Jan 2012, at 12:29, Galder Zamarreño wrote:
On Jan 10, 2012, at 12:59 PM, Sérgio Miguel Fernandes wrote:
I guess this is also a 5.0 to 5.1 issue:
https://issues.jboss.org/browse/ISPN-1696
In what way is that an
Hi,
On 9 Jan 2012, at 10:26, Galder Zamarreño wrote:
We need to document a list of gotcha's related to 5.0 to 5.1 upgrades as we
prepare for final. So far I have noted these myself:
- wakeUpInterval now defined only via expiration (XSD allowds wakeUpInterval
in eviction but new parser
That's a bug. It's fixed in CR3 :-)
On 10 Jan 2012, at 11:59, Sérgio Miguel Fernandes wrote:
Hi,
On 9 Jan 2012, at 10:26, Galder Zamarreño wrote:
We need to document a list of gotcha's related to 5.0 to 5.1 upgrades as we
prepare for final. So far I have noted these myself:
-
Just did it: https://issues.jboss.org/browse/ISPN-1695
On Jan 9, 2012, at 12:37 PM, Manik Surtani wrote:
On 9 Jan 2012, at 10:27, Galder Zamarreño wrote:
^, btw, this gotcha could be removed by making the parser deal with
wakeUpInterval in eviction and passing it onto the expiration
On 9 Jan 2012, at 10:56, Mircea Markus wrote:
Default transaction enlistment is now Synchronisation (vs XAResource).
No it's not - I haven't submitted that pull request yet. The work is in my
topic branch
https://github.com/maniksurtani/infinispan/tree/t_1284
but I have concerns around
On 9 Jan 2012, at 13:38, Manik Surtani wrote:
On 9 Jan 2012, at 10:56, Mircea Markus wrote:
Default transaction enlistment is now Synchronisation (vs XAResource).
No it's not - I haven't submitted that pull request yet. The work is in my
topic branch
