http://nagoya.apache.org/bugzilla/show_bug.cgi?id=497

*** shadow/497  Fri Jun  8 14:17:29 2001
--- shadow/497.tmp.12818        Tue Jun 12 18:57:03 2001
***************
*** 2,9 ****
  | ORO dies while trying to match a String with wierd characters BugRat Repor |
  +----------------------------------------------------------------------------+
  |        Bug #: 497                         Product: ORO                     |
! |       Status: UNCONFIRMED                 Version: Unknown                 |
! |   Resolution:                            Platform: All                     |
  |     Severity: Normal                   OS/Version: All                     |
  |     Priority: High                      Component: Main                    |
  +----------------------------------------------------------------------------+
--- 2,9 ----
  | ORO dies while trying to match a String with wierd characters BugRat Repor |
  +----------------------------------------------------------------------------+
  |        Bug #: 497                         Product: ORO                     |
! |       Status: RESOLVED                    Version: Unknown                 |
! |   Resolution: FIXED                      Platform: All                     |
  |     Severity: Normal                   OS/Version: All                     |
  |     Priority: High                      Component: Main                    |
  +----------------------------------------------------------------------------+
***************
*** 20,22 ****
--- 20,30 ----
  
  ------- Additional Comments From [EMAIL PROTECTED]  2001-06-08 14:17 -------
  Reassigning from tomcat-dev to oro-dev.
+ 
+ ------- Additional Comments From [EMAIL PROTECTED]  2001-06-12 18:57 -------
+ Even though no sample code has been provided, it is clear that this was
+ caused only when a character class was used in the pattern because character
+ classes only supported 8 bit characters until recently.  Given that Unicode
+ support has been implemented for character classes, I'm going to mark the
+ bug as fixed and then close it.  If the problem persists for the user, a
+ new bug should be opened and sample code provided.

Reply via email to