[Bug 2052] New: API: Avoid ever creating Request objects without a receiver

[bugzilla-daemon at icedtea.classpath.org]

http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=2052

            Bug ID: 2052
           Summary: API: Avoid ever creating Request objects without a
                    receiver
           Product: Thermostat
           Version: hg
          Hardware: x86_64
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: Thermostat
          Assignee: unassigned at icedtea.classpath.org
          Reporter: omajid at redhat.com
                CC: thermostat at icedtea.classpath.org

The Request API currently allows the creation of requests without a receiever.
The agent encounters a NullPointerException when it tries to handle them, and
no reply (not even ERROR) is ever sent to the client. In my test, the client
hung until I killed it.

A Request without a receiver set is essentially a mistake by the developer
trying to use the Request API. We should try and limit such mistakes. Each
Request object requires a target (in the constructor); it should also require a
receiver.

On a slightly different note, should a receiver be part of the request API at
all? Seems more flexible if anything that wants to handle a request can handle
it.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/distro-pkg-dev/attachments/20141027/0865415e/attachment.html>