You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2011/08/21 16:53:27 UTC

[jira] [Created] (QPID-3439) stop importing Signal handling classes directly to break reliance on sun.misc heirarchy and prevent the associated compiler warnings

stop importing Signal handling classes directly to break reliance on sun.misc heirarchy and prevent the associated compiler warnings
------------------------------------------------------------------------------------------------------------------------------------

                 Key: QPID-3439
                 URL: https://issues.apache.org/jira/browse/QPID-3439
             Project: Qpid
          Issue Type: Improvement
          Components: Java Broker
    Affects Versions: 0.10, 0.9, 0.8, 0.7, 0.6, 0.5, 0.11, 0.12
            Reporter: Robbie Gemmell
            Assignee: Robbie Gemmell
             Fix For: 0.13


The broker currently uses the sun.misc.Signal(Handler) classes directly within the ServerConfiguration class, creating both a reliance on the classes existing (they are far more prevalent than just the Sun JDK as might be expected, but their existance isn't guaranteed) and also causing unsuppressable compiler warnigns during the build.

The use of these classes should be isolated from ServerConfiguration to allow use of the broker on JDKs which do not support them, and additionally their use should be proxied using reflection to remove the associated compiler warnings.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


[jira] [Assigned] (QPID-3439) stop importing Signal handling classes directly to break reliance on sun.misc heirarchy and prevent the associated compiler warnings

Posted by "Robbie Gemmell (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robbie Gemmell reassigned QPID-3439:
------------------------------------

    Assignee: Keith Wall  (was: Robbie Gemmell)

Hi Keith, could you review please?

> stop importing Signal handling classes directly to break reliance on sun.misc heirarchy and prevent the associated compiler warnings
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-3439
>                 URL: https://issues.apache.org/jira/browse/QPID-3439
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>    Affects Versions: 0.5, 0.6, 0.7, 0.8, 0.9, 0.10, 0.11, 0.12
>            Reporter: Robbie Gemmell
>            Assignee: Keith Wall
>             Fix For: 0.13
>
>
> The broker currently uses the sun.misc.Signal(Handler) classes directly within the ServerConfiguration class, creating both a reliance on the classes existing (they are far more prevalent than just the Sun JDK as might be expected, but their existance isn't guaranteed) and also causing unsuppressable compiler warnigns during the build.
> The use of these classes should be isolated from ServerConfiguration to allow use of the broker on JDKs which do not support them, and additionally their use should be proxied using reflection to remove the associated compiler warnings.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


[jira] [Updated] (QPID-3439) stop importing Signal handling classes directly to break reliance on sun.misc heirarchy and prevent the associated compiler warnings

Posted by "Robbie Gemmell (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robbie Gemmell updated QPID-3439:
---------------------------------

    Status: Ready To Review  (was: In Progress)

> stop importing Signal handling classes directly to break reliance on sun.misc heirarchy and prevent the associated compiler warnings
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-3439
>                 URL: https://issues.apache.org/jira/browse/QPID-3439
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>    Affects Versions: 0.5, 0.6, 0.7, 0.8, 0.9, 0.10, 0.11, 0.12
>            Reporter: Robbie Gemmell
>            Assignee: Robbie Gemmell
>             Fix For: 0.13
>
>
> The broker currently uses the sun.misc.Signal(Handler) classes directly within the ServerConfiguration class, creating both a reliance on the classes existing (they are far more prevalent than just the Sun JDK as might be expected, but their existance isn't guaranteed) and also causing unsuppressable compiler warnigns during the build.
> The use of these classes should be isolated from ServerConfiguration to allow use of the broker on JDKs which do not support them, and additionally their use should be proxied using reflection to remove the associated compiler warnings.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


[jira] [Resolved] (QPID-3439) stop importing Signal handling classes directly to break reliance on sun.misc heirarchy and prevent the associated compiler warnings

Posted by "Keith Wall (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Keith Wall resolved QPID-3439.
------------------------------

    Resolution: Fixed

Reviewed, no comments from me. 

cheers Keith.

> stop importing Signal handling classes directly to break reliance on sun.misc heirarchy and prevent the associated compiler warnings
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-3439
>                 URL: https://issues.apache.org/jira/browse/QPID-3439
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>    Affects Versions: 0.5, 0.6, 0.7, 0.8, 0.9, 0.10, 0.11, 0.12
>            Reporter: Robbie Gemmell
>            Assignee: Keith Wall
>             Fix For: 0.13
>
>
> The broker currently uses the sun.misc.Signal(Handler) classes directly within the ServerConfiguration class, creating both a reliance on the classes existing (they are far more prevalent than just the Sun JDK as might be expected, but their existance isn't guaranteed) and also causing unsuppressable compiler warnigns during the build.
> The use of these classes should be isolated from ServerConfiguration to allow use of the broker on JDKs which do not support them, and additionally their use should be proxied using reflection to remove the associated compiler warnings.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org