[JBoss JIRA] (ISPN-820) Resolve {@link} links in configuration reference
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-820?page=com.atlassian.jira.plugin.s... ]
Mircea Markus updated ISPN-820:
-------------------------------
Component/s: Documentation-Core
> Resolve {@link} links in configuration reference
> -------------------------------------------------
>
> Key: ISPN-820
> URL: https://issues.jboss.org/browse/ISPN-820
> Project: Infinispan
> Issue Type: Feature Request
> Components: Documentation-Core
> Reporter: Galder Zamarreño
> Assignee: Pete Muir
>
> Currently configuration reference documentation does not resolve {@link} links.
> It'd be nice if it'd point to the javadoc of the corresponding class if available!
> Examples:
> - Fully qualified class name of a class that looks up a reference to a {@link javax.transaction.TransactionManager}. The default provided is capable of locating the default TransactionManager in most popular Java EE systems, using a JNDI lookup. (Javadoc)
> - Fully qualified name of the class that the configured {@link org.infinispan.marshall.Externalizer} can marshall/unmarshall. Establishing the link between type marshalled and {@link org.infinispan.marshall.Externalizer} implementations enables users to provide their own marshalling mechanisms even for classes which they cannot modify or extend. (Javadoc)
--
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
12 years, 2 months
[JBoss JIRA] (ISPN-230) Enable JNDI binding of Cache/CacheManager out of the box
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-230?page=com.atlassian.jira.plugin.s... ]
Mircea Markus resolved ISPN-230.
--------------------------------
Resolution: Rejected
see galder's last comment
> Enable JNDI binding of Cache/CacheManager out of the box
> --------------------------------------------------------
>
> Key: ISPN-230
> URL: https://issues.jboss.org/browse/ISPN-230
> Project: Infinispan
> Issue Type: Feature Request
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Priority: Minor
> Labels: hackathon
>
> Note that implementing this has no urgency since it does not really help Brian S for the JBoss AS integration.
> See: http://lists.jboss.org/pipermail/infinispan-dev/2009-October/001663.html
> So, I'm thinking that we could have a <jndi name="xyz"/> configuration
> option both at the global level (for Cache Manager) and at the Cache
> level. So,
> - if <jndi/> was present in the global section, we'd bind CacheManager
> to java:CacheManager
> - if <jndi name="xyz"/> was present in the global section, we'd bind
> CacheManager to java:xyz
> - if <jndi/> was present in the cache section, we'd bind Cache to
> java:<name-of-the-cache>
> - if <jndi name="xyz"/> was present in the cache section, we'd bind
> Cache to java:xyz
--
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
12 years, 2 months
[JBoss JIRA] (ISPN-317) when unsafeReturnValues is false, combine put, remove, replace, putIfAbsent, to pull back responses in 1 command
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-317?page=com.atlassian.jira.plugin.s... ]
Mircea Markus updated ISPN-317:
-------------------------------
Priority: Minor (was: Major)
> when unsafeReturnValues is false, combine put, remove, replace, putIfAbsent, to pull back responses in 1 command
> ----------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-317
> URL: https://issues.jboss.org/browse/ISPN-317
> Project: Infinispan
> Issue Type: Feature Request
> Affects Versions: 5.1.0.FINAL
> Reporter: Mircea Markus
> Assignee: Manik Surtani
> Priority: Minor
>
> at the moment this is split in two operations: a remote get followed by an put. Optimize this to only reside in one operation.
--
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
12 years, 2 months
[JBoss JIRA] (ISPN-317) when unsafeReturnValues is false, combine put, remove, replace, putIfAbsent, to pull back responses in 1 command
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-317?page=com.atlassian.jira.plugin.s... ]
Mircea Markus updated ISPN-317:
-------------------------------
Component/s: Core
> when unsafeReturnValues is false, combine put, remove, replace, putIfAbsent, to pull back responses in 1 command
> ----------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-317
> URL: https://issues.jboss.org/browse/ISPN-317
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 5.1.0.FINAL
> Reporter: Mircea Markus
> Assignee: Manik Surtani
> Priority: Minor
>
> at the moment this is split in two operations: a remote get followed by an put. Optimize this to only reside in one operation.
--
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
12 years, 2 months
[JBoss JIRA] (ISPN-1409) Introduce a binary-stream upgrading CacheLoader
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-1409?page=com.atlassian.jira.plugin.... ]
Mircea Markus resolved ISPN-1409.
---------------------------------
Resolution: Rejected
see last comment.
> Introduce a binary-stream upgrading CacheLoader
> -----------------------------------------------
>
> Key: ISPN-1409
> URL: https://issues.jboss.org/browse/ISPN-1409
> Project: Infinispan
> Issue Type: Feature Request
> Reporter: Sanne Grinovero
> Assignee: Manik Surtani
>
> We need a CacheLoader decorator able to chain sets of two different Externalizers which are targeting the same Java type to transform from one binary format to the next binary format.
> Example: a Person object stored in the cache and an Externalizer is coupled to it. In a new release the Externalizer is changed to provide a different binary representation. Using the old one the stream is transformed from a byte[] to a Person, then this Java instance is feed to the new Externalizer implementation to get the new corresponding byte[]; the updated stream is stored in the decorated CacheLoader so that the nodes going to be attached to the cache store and using the new Externalizer will be fine.
> A little complexity is introduced if the cache has to know about different sets of Externalizers if several different types need to be upgraded. A possible solution is to use a single decorator instance for each type, creating a chain of decorators if they are able to pass "as is" each externalizer id they are not directly coupled to.
--
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
12 years, 2 months