You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jcs-dev@jakarta.apache.org by "Dmitry Savenko (JIRA)" <ji...@apache.org> on 2009/02/11 10:42:59 UTC
[jira] Commented: (JCS-47) How to build an element key
[ https://issues.apache.org/jira/browse/JCS-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672567#action_12672567 ]
Dmitry Savenko commented on JCS-47:
-----------------------------------
Could anybody from development team update this task, please?
There are no any recommendation in docs how to create key.
What is the pros/cons creation key as a String with delimiter?
Are there any benefits to prefer String vs object PK with overwritten hashCode() and equals()?
> How to build an element key
> ---------------------------
>
> Key: JCS-47
> URL: https://issues.apache.org/jira/browse/JCS-47
> Project: JCS
> Issue Type: Question
> Components: Documentation
> Affects Versions: jcs-1.3
> Reporter: Ronny Roeller
> Assignee: Aaron Smuts
>
> I use a string as key for my elements. Now I was surprised to get this error message:
> 11:07:52,257 INFO [CacheEventQueue] Cache event queue created: CacheEventQueue [listenerId=1501085802, cacheName=cache]
> 11:07:53,000 INFO [STDOUT] org.apache.jcs.access.exception.CacheException: key must not end with : for a put operation
> I guess this means that colon is a special character, and can't be freely used as a key.
> Unfortunately, I couldn't find any documentation on the project website what the constrains are for keys. It would also be interested to know if there is anything else to be considered when choosing the key, e.g. is there an advantage in using shorter keys?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
RE: [jira] Commented: (JCS-47) How to build an element key
Posted by Tim Cronin <tc...@interwoven.com>.
Does this help?
http://jakarta.apache.org/jcs/faq.html#hierarchical-removal
-----Original Message-----
From: Dmitry Savenko (JIRA) [mailto:jira@apache.org]
Sent: Wednesday, February 11, 2009 3:43 AM
To: jcs-dev@jakarta.apache.org
Subject: [jira] Commented: (JCS-47) How to build an element key
[
https://issues.apache.org/jira/browse/JCS-47?page=com.atlassian.jira.plu
gin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672567#act
ion_12672567 ]
Dmitry Savenko commented on JCS-47:
-----------------------------------
Could anybody from development team update this task, please?
There are no any recommendation in docs how to create key.
What is the pros/cons creation key as a String with delimiter?
Are there any benefits to prefer String vs object PK with overwritten
hashCode() and equals()?
> How to build an element key
> ---------------------------
>
> Key: JCS-47
> URL: https://issues.apache.org/jira/browse/JCS-47
> Project: JCS
> Issue Type: Question
> Components: Documentation
> Affects Versions: jcs-1.3
> Reporter: Ronny Roeller
> Assignee: Aaron Smuts
>
> I use a string as key for my elements. Now I was surprised to get this
error message:
> 11:07:52,257 INFO [CacheEventQueue] Cache event queue created:
CacheEventQueue [listenerId=1501085802, cacheName=cache]
> 11:07:53,000 INFO [STDOUT]
org.apache.jcs.access.exception.CacheException: key must not end with :
for a put operation
> I guess this means that colon is a special character, and can't be
freely used as a key.
> Unfortunately, I couldn't find any documentation on the project
website what the constrains are for keys. It would also be interested to
know if there is anything else to be considered when choosing the key,
e.g. is there an advantage in using shorter keys?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org