You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Niall Pemberton (JIRA)" <ji...@apache.org> on 2010/02/03 00:51:18 UTC
[jira] Commented: (LANG-76) [lang] EnumUtils.getEnum() doesn't work
well in 1.5
[ https://issues.apache.org/jira/browse/LANG-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828847#action_12828847 ]
Niall Pemberton commented on LANG-76:
-------------------------------------
So whats the solution for this? I've never looked at Lang's enums, anyone care to submit a patch as I'm hoping to do a 2.5 release
> [lang] EnumUtils.getEnum() doesn't work well in 1.5
> ---------------------------------------------------
>
> Key: LANG-76
> URL: https://issues.apache.org/jira/browse/LANG-76
> Project: Commons Lang
> Issue Type: Bug
> Components: lang.enums.*
> Affects Versions: 2.1
> Environment: Operating System: other
> Platform: Other
> Reporter: Igor Laberov
> Fix For: 2.x
>
>
> Hi,
> I encountered with problem using EnumUtils.getEnum() in 1.5. It appears that my
> Enum class should be accessed first so constructor will be called. In 1.4 it was
> enough to have myClass.class, so all static members were initialized. In 1.5 it
> doesn't work.
> I noticed that static members are not initialized anymore while acessing to
> class definition. See the code
> public class Test {
> public static final class TT{
> public static final TT one = new TT();
> private TT(){
> System.out.println("Called TT" );
> }
> }
>
> public static void main(String[] args) {
> Class cl = TT.class;
> // System.out.println( TT.one);
> // System.out.println(TT.class.isAssignableFrom(String.class));
> }
> }
> In 1.4 constructor of TT is called, while in 1.5 is not.
> Actually, according to the spec
> (http://java.sun.com/docs/books/jls/second_edition/html/execution.doc.html#57946),
> this is right behavior of Java.
> Unfortunately, I didn't succeded to think about good solution..
> P.s. I know that in 1.5 we have enum built-in, but it is not the same, and we
> try to move to 1.5 without too much changes
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.