An admin console issue that was filed related to multibyte characters in
cluster name :
http://java.net/jira/browse/GLASSFISH-15705
Also, are multibyte characters supposed to be supported for other
things. For example, a multibyte character in the name of a lifecycle
module results in this issue :
http://java.net/jira/browse/GLASSFISH-15707
On 1/27/11 3:01 PM, Tom Mueller wrote:
> Today, issue 15706 was filed because of an English error message being
> generated when multibyte character is used in an instance name.
> http://java.net/jira/browse/GLASSFISH-15706
>
> While looking into this, I was wondering why such an instance name was
> even allowed since instance names are only supposed to contain
> letters, numbers and some special characters. As it turns out, the
> regular expression that is used for validating the name uses "\p{L}"
> for letters, which means any Unicode character that is a letter, not
> just ASCII letters. In my test, I was able to create an instance with
> a multibyte character, but then I couldn't start it or delete it from
> the console because I get an IllegalArgumentException from the REST
> interface (see the bug report for details).
>
> So my question is this - do we really support creation of instances
> with multibyte characters in their names?
>
> If no, then we need to change the regex that is used to validate the
> name.
> If yes, then we might have lots of bug fixing to do to get this to
> work end-to-end.
>
> Does anybody know what 2.1 supports here?
>
> Tom
>
>
>