river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ron Mann (JIRA)" <j...@apache.org>
Subject [jira] Created: (RIVER-120) ConfigurationFile spec should require Java lexical behavior
Date Fri, 27 Jul 2007 18:57:53 GMT
ConfigurationFile spec should require Java lexical behavior
-----------------------------------------------------------

                 Key: RIVER-120
                 URL: https://issues.apache.org/jira/browse/RIVER-120
             Project: River
          Issue Type: Improvement
          Components: net_jini_config
    Affects Versions: jtsk_2.1
            Reporter: Ron Mann
            Priority: Minor


Bugtraq ID [4848056|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4848056]
The specification for the ConfigurationFile class should require that parsing
follow the rules for lexical structure in the Java Language Specification, both
for the contents of the configuration file and for override options.

In particular, although the current implementation supports Unicode escape
characters when parsing configuration files, via a Reader, or in override
options, the specification only explicitly requires support for escapes in 
String and character literals.  Being able to specify Unicode escapes in
override options is a useful feature, so it should be part of the specification.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message