You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <de...@db.apache.org> on 2005/04/26 20:06:25 UTC

[jira] Created: (DERBY-240) loading special locale fails with jdk131 and jars

loading special locale fails with jdk131 and jars
-------------------------------------------------

         Key: DERBY-240
         URL: http://issues.apache.org/jira/browse/DERBY-240
     Project: Derby
        Type: Bug
  Components: Localization  
    Versions: 10.1.0.0    
 Environment: IBM and Sun jdk131 and jars
    Reporter: Myrna van Lunteren
    Priority: Trivial


With the jdk131 & ibm131 & running with jars, a special test locale qq_PP_testOnly with which the database gets created does not appear to get loaded, instead, the default locale set using java.util.Locale.setDefault() is used.

When using classes in a directory, this does not happen. Running with jdk141 or jdk15(i.e. 5.0), either jars or classes, the locale also gets loaded correctly.
This looks like a jvm bug, however, as it's working correctly with later versions of the jvms, a fix is unlikely.

Affected test: i18n/messageLocale.sql


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Closed: (DERBY-240) loading special locale fails with jdk131 and jars

Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-240?page=all ]
     
Andrew McIntyre closed DERBY-240:
---------------------------------


> loading special locale fails with jdk131 and jars
> -------------------------------------------------
>
>          Key: DERBY-240
>          URL: http://issues.apache.org/jira/browse/DERBY-240
>      Project: Derby
>         Type: Bug
>   Components: Localization
>     Versions: 10.1.1.0
>  Environment: IBM and Sun jdk131 and jars
>     Reporter: Myrna van Lunteren
>     Assignee: Myrna van Lunteren
>     Priority: Trivial
>      Fix For: 10.1.1.0

>
> With the jdk131 & ibm131 & running with jars, a special test locale qq_PP_testOnly with which the database gets created does not appear to get loaded, instead, the default locale set using java.util.Locale.setDefault() is used.
> When using classes in a directory, this does not happen. Running with jdk141 or jdk15(i.e. 5.0), either jars or classes, the locale also gets loaded correctly.
> This looks like a jvm bug, however, as it's working correctly with later versions of the jvms, a fix is unlikely.
> Affected test: i18n/messageLocale.sql

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Resolved: (DERBY-240) loading special locale fails with jdk131 and jars

Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-240?page=all ]
     
Andrew McIntyre resolved DERBY-240:
-----------------------------------

    Fix Version: 10.1.1.0
     Resolution: Won't Fix
      Assign To: Myrna van Lunteren

Closing as Won't Fix. Test excluded from jdk131, I doubt anyone has the itch to chase this down.

> loading special locale fails with jdk131 and jars
> -------------------------------------------------
>
>          Key: DERBY-240
>          URL: http://issues.apache.org/jira/browse/DERBY-240
>      Project: Derby
>         Type: Bug
>   Components: Localization
>     Versions: 10.1.1.0
>  Environment: IBM and Sun jdk131 and jars
>     Reporter: Myrna van Lunteren
>     Assignee: Myrna van Lunteren
>     Priority: Trivial
>      Fix For: 10.1.1.0

>
> With the jdk131 & ibm131 & running with jars, a special test locale qq_PP_testOnly with which the database gets created does not appear to get loaded, instead, the default locale set using java.util.Locale.setDefault() is used.
> When using classes in a directory, this does not happen. Running with jdk141 or jdk15(i.e. 5.0), either jars or classes, the locale also gets loaded correctly.
> This looks like a jvm bug, however, as it's working correctly with later versions of the jvms, a fix is unlikely.
> Affected test: i18n/messageLocale.sql

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (DERBY-240) loading special locale fails with jdk131 and jars

Posted by "Samuel Andrew McIntyre (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-240?page=comments#action_63855 ]
     
Samuel Andrew McIntyre commented on DERBY-240:
----------------------------------------------

Test excluded from running in jdk131 with revision 164903.

> loading special locale fails with jdk131 and jars
> -------------------------------------------------
>
>          Key: DERBY-240
>          URL: http://issues.apache.org/jira/browse/DERBY-240
>      Project: Derby
>         Type: Bug
>   Components: Localization
>     Versions: 10.1.0.0
>  Environment: IBM and Sun jdk131 and jars
>     Reporter: Myrna van Lunteren
>     Priority: Trivial

>
> With the jdk131 & ibm131 & running with jars, a special test locale qq_PP_testOnly with which the database gets created does not appear to get loaded, instead, the default locale set using java.util.Locale.setDefault() is used.
> When using classes in a directory, this does not happen. Running with jdk141 or jdk15(i.e. 5.0), either jars or classes, the locale also gets loaded correctly.
> This looks like a jvm bug, however, as it's working correctly with later versions of the jvms, a fix is unlikely.
> Affected test: i18n/messageLocale.sql

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira