8000 Java RMI: handling of null arguments in remote API · Issue #55 · rolandweber/Pityoulish · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
This repository was archived by the owner on Nov 21, 2021. It is now read-only.
This repository was archived by the owner on Nov 21, 2021. It is now read-only.
Java RMI: handling of null arguments in remote API #55
Open
@rolandweber

Description

@rolandweber

follow-up from #11:

  • Should null arguments be reported as an ApiException or as a NullPointerException (NPE)?
  • Should the exception be logged?

Currently, the sanity checkers throw an NPE, which is not logged. But RemoteOutletManagerImpl.publishOutlet logs the NPE for a null outlet. So that method throws a logged NPE if the outlet is null, but an unlogged NPE if the ticket token is null. Decide on one behavior, then implement that consistently across the remote API of the server.

If the behavior of the sanity checkers changes, this will affect the Socket-based server, too.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0