Hi Chris, Tom,
I did some testing on this two years ago (V2.1 & V3).
As I couldn't find an answer on whether multibyte characters were
(consistently/officially) supported at all, I pointed out an
inconsistency between what a field's description said and what was
actually accepted.
http://java.net/jira/browse/GLASSFISH-7134
I didn't feel there was much interest in the dev mailing list to sort
out and fix these type of issues so I stopped reporting them.
If you can make it clear where (if anywhere) you want to support
multibyte characters (also in the manual - users must be just as
confused as the developers following this thread), maybe I can help (for
V3.2 onwards) to report field descriptions, validation code and manual
entries that don't follow it.
Regards,
Dies
> -----Original Message-----
> From: Chris Kasso [mailto:chris.kasso_at_oracle.com]
> Sent: Friday, 28 January 2011 08:39
> To: admin_at_glassfish.java.net; Tom Mueller
> Subject: Re: multibyte characters in instance names
>
> Did these issues exist with 3.0.1? I'm trying to understand the
extent
> of this regression.
>
> And the $64k question is why are these tests just now being executed.
> Why weren't these issues found months ago? Sigh.
>
> On 01/27/11 12:52, Tom Mueller wrote:
> > Thanks Anissa for checking on this. So these are bugs then.
> > Does the REST team want yet another bug filed for the
> > IllegalArgumentException or should I just tack this on to issue
15705?
> >
> > Thanks.
> > Tom
> >
> > On 1/27/2011 2:14 PM, Anissa Lam wrote:
> >>
> >> I just checked, we do support multibyte char in v2. See attached.
> >>
> >> Anissa.
> >>
> >> On 1/27/11 12: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