June 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2810) In REST, default values for maxIdleTimeSeconds and timeToLiveSeconds should be 0

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2810?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-2810: ---------------------------------------- This is a valid point, but it's a bit late to start changing the REST protocol, and we'd need to see with Tristan about changing the protocol for the product. > In REST, default values for maxIdleTimeSeconds and timeToLiveSeconds should be 0 > -------------------------------------------------------------------------------- > > Key: ISPN-2810 > URL: https://issues.jboss.org/browse/ISPN-2810 > Project: Infinispan > Issue Type: Feature Request > Components: Remote protocols > Affects Versions: 5.2.0.Final > Reporter: Dan Berindei > Assignee: Galder Zamarreño > Fix For: 5.3.0.Final > > > Contrary to what ISPN-732 says, timeToLiveSeconds=0 and maxIdleTimeSeconds=0 are now treated correctly by the server and the entry is stored in the cache with the default lifespan/maxIdle. > But if the user PUTs or POSTs an entry and doesn't specify timeToLiveSeconds=0 and maxIdleTimeSeconds=0 explicitly, the entries are stored with infinite lifespan/maxIdle. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2810) In REST, default values for maxIdleTimeSeconds and timeToLiveSeconds should be 0

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2810?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-2810: ---------------------------------------- Late in 5.3.x series I mean. > In REST, default values for maxIdleTimeSeconds and timeToLiveSeconds should be 0 > -------------------------------------------------------------------------------- > > Key: ISPN-2810 > URL: https://issues.jboss.org/browse/ISPN-2810 > Project: Infinispan > Issue Type: Feature Request > Components: Remote protocols > Affects Versions: 5.2.0.Final > Reporter: Dan Berindei > Assignee: Galder Zamarreño > Fix For: 5.3.0.Final > > > Contrary to what ISPN-732 says, timeToLiveSeconds=0 and maxIdleTimeSeconds=0 are now treated correctly by the server and the entry is stored in the cache with the default lifespan/maxIdle. > But if the user PUTs or POSTs an entry and doesn't specify timeToLiveSeconds=0 and maxIdleTimeSeconds=0 explicitly, the entries are stored with infinite lifespan/maxIdle. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2810) In REST, default values for maxIdleTimeSeconds and timeToLiveSeconds should be 0

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2810?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2810: ----------------------------------- Fix Version/s: 6.0.0.Final (was: 5.3.0.Final) > In REST, default values for maxIdleTimeSeconds and timeToLiveSeconds should be 0 > -------------------------------------------------------------------------------- > > Key: ISPN-2810 > URL: https://issues.jboss.org/browse/ISPN-2810 > Project: Infinispan > Issue Type: Feature Request > Components: Remote protocols > Affects Versions: 5.2.0.Final > Reporter: Dan Berindei > Assignee: Galder Zamarreño > Fix For: 6.0.0.Final > > > Contrary to what ISPN-732 says, timeToLiveSeconds=0 and maxIdleTimeSeconds=0 are now treated correctly by the server and the entry is stored in the cache with the default lifespan/maxIdle. > But if the user PUTs or POSTs an entry and doesn't specify timeToLiveSeconds=0 and maxIdleTimeSeconds=0 explicitly, the entries are stored with infinite lifespan/maxIdle. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3238) infinispan-config-5.3.xsd missing "compatibility" element

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3238?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3238: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > infinispan-config-5.3.xsd missing "compatibility" element > --------------------------------------------------------- > > Key: ISPN-3238 > URL: https://issues.jboss.org/browse/ISPN-3238 > Project: Infinispan > Issue Type: Feature Request > Components: Documentation > Affects Versions: 5.3.0.CR2 > Reporter: Erik Pearson > Assignee: Galder Zamarreño > Priority: Critical > Fix For: 5.3.0.Final > > > The schema documentation for and publicly available http://www.jboss.org/schema/infinispan/infinispan-config-5.3.xsd are missing the "compatibility" element under default/namedCache. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3259) Introduce a BOM to be shared between Infinispan Library and Server

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-3259: ------------------------------------- Summary: Introduce a BOM to be shared between Infinispan Library and Server Key: ISPN-3259 URL: https://issues.jboss.org/browse/ISPN-3259 Project: Infinispan Issue Type: Sub-task Components: Build process Reporter: Tristan Tarrant Assignee: Mircea Markus Fix For: 6.0.0.Alpha1, 6.0.0.Final Move all core dependency management information to a top-level BOM file and use that to share GAVs between library and server -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3259) Introduce a BOM to be shared between Infinispan Library and Server

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3259?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-3259: ------------------------------------- Assignee: Tristan Tarrant (was: Mircea Markus) > Introduce a BOM to be shared between Infinispan Library and Server > ------------------------------------------------------------------ > > Key: ISPN-3259 > URL: https://issues.jboss.org/browse/ISPN-3259 > Project: Infinispan > Issue Type: Sub-task > Components: Build process > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 6.0.0.Alpha1, 6.0.0.Final > > > Move all core dependency management information to a top-level BOM file and use that to share GAVs between library and server -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2753) Drop the staxmapper dependency

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2753?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2753: ---------------------------------- Parent: ISPN-3212 Issue Type: Sub-task (was: Enhancement) > Drop the staxmapper dependency > ------------------------------ > > Key: ISPN-2753 > URL: https://issues.jboss.org/browse/ISPN-2753 > Project: Infinispan > Issue Type: Sub-task > Components: Configuration > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 6.0.0.Alpha1, 6.0.0.Final > > > staxmapper is composed of very few classes, of which we only use half. In order to minimize the number of dependencies, the logic of staxmapper can be incorporated in Infinispan, tailored to our own specific needs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2753) Drop the staxmapper dependency

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2753?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2753: ---------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/infinispan/infinispan/pull/1914 (was: https://github.com/infinispan/infinispan/pull/1607) > Drop the staxmapper dependency > ------------------------------ > > Key: ISPN-2753 > URL: https://issues.jboss.org/browse/ISPN-2753 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 6.0.0.Alpha1, 6.0.0.Final > > > staxmapper is composed of very few classes, of which we only use half. In order to minimize the number of dependencies, the logic of staxmapper can be incorporated in Infinispan, tailored to our own specific needs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3246) Clean up Tools module

by Navin Surtani (JIRA)

[ https://issues.jboss.org/browse/ISPN-3246?page=com.atlassian.jira.plugin.... ] Navin Surtani resolved ISPN-3246. --------------------------------- Resolution: Done There aren't any usages of the deprecated configuration package in this module. > Clean up Tools module > --------------------- > > Key: ISPN-3246 > URL: https://issues.jboss.org/browse/ISPN-3246 > Project: Infinispan > Issue Type: Sub-task > Components: Migration tools > Affects Versions: 6.0.0.Alpha1, 6.0.0.Beta1 > Reporter: Navin Surtani > Assignee: Navin Surtani > Fix For: 6.0.0.Beta1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2463) Clean up Configuration API in test suites

by Navin Surtani (JIRA)

[ https://issues.jboss.org/browse/ISPN-2463?page=com.atlassian.jira.plugin.... ] Navin Surtani updated ISPN-2463: -------------------------------- Description: For ISPN 6.x, the package org.infinispan.config needs to be deleted. We need to go through each individual module and clean out every usage of this package (specifically the testsuite) and migrate all usages of the org.infinispan.config API to the org.infinispan.configuration.cache API. A sub-task for each module should be created so that it would make easier tracking of individual pull-requests. was:The test-suite currently uses older, previous implementations of configuring Infinispan. These approaches are currently deprecated and for ease of maintenance it would be useful to clean up the approach used to configure Infinispan within the test-suite. > Clean up Configuration API in test suites > ----------------------------------------- > > Key: ISPN-2463 > URL: https://issues.jboss.org/browse/ISPN-2463 > Project: Infinispan > Issue Type: Task > Components: Test Suite > Affects Versions: 6.0.0.Alpha1, 6.0.0.Beta1 > Reporter: Navin Surtani > Assignee: Navin Surtani > Labels: configuration, testsuite > Fix For: 6.0.0.Beta1 > > > For ISPN 6.x, the package org.infinispan.config needs to be deleted. We need to go through each individual module and clean out every usage of this package (specifically the testsuite) and migrate all usages of the org.infinispan.config API to the org.infinispan.configuration.cache API. > A sub-task for each module should be created so that it would make easier tracking of individual pull-requests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2013