[
http://jira.jboss.com/jira/browse/JBCACHE-644?page=all ]
Galder Zamarreno resolved JBCACHE-644.
--------------------------------------
Resolution: Done
Substituting invalid characters for invalid characters would be quite an
overhead for FCL.
If you wanna avoid portability issues, don't use certain characters which
are not recommended for FCL or Fqn.
As a result, warnings are being logged so that users are aware that
using some of the characters could affect the portability of their application:
- When creating an FCL root location, check for any non portable
characters throwing a warning. Checks '*' '<' '>'
'|' '"' '?'
- When storing attributes, check that the Fqn tree does not contain non
portable characters. Checks '*' '<' '>' '|'
'"' '?' and also '\' '/' and ':'
- When storing attributes as well, check for entire path that could be
bigger than 255 characters throwing a warning.
FileCacheLoader fails if FQN contains illegal/too many characters
-----------------------------------------------------------------
Key: JBCACHE-644
URL:
http://jira.jboss.com/jira/browse/JBCACHE-644
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Cache loaders
Affects Versions: 1.2, 1.2.1, 1.2.2, 1.2.3, 1.2.4beta, 1.3.0.GA, 1.2.4, 1.2.4SP1,
1.2.4SP2, 1.3.0.SP1, 1.3.0.SP2
Environment: Windows XP
Reporter: Amit Kasher
Assigned To: Galder Zamarreno
Fix For: 2.0.0.GA
Time Spent: 4 hours
Remaining Estimate: 0 minutes
When putting FQNs that are too long to become filenames, or that contain illlegal
characters for filenames (semicolon, for example), the FileCacheLoader throws an
IOException.
The FileCacheLoader should encode the FQN string so that it is a valid filename.
--
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