Skip to content

Conversation

@Tmarks
Copy link

@Tmarks Tmarks commented Aug 15, 2013

Added the ConnectionException class from the old j2bugzilla code, and made all overloads of Bugzilla.connectTo() throw this exception, just as the BugzillaConnector did.

Tmarks added 2 commits May 18, 2013 15:35
…zilla implementation. It belonged here because the BugzillaConnector throws it from its connectTo() methods, but the Bugzilla class did not.

This was also changed; Bugzilla's connectTo() methods now throw ConnectionException in their signatures.
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When I first wrote the alpha for J2Bugzilla, I was solidly in the checked exception camp. Now I'm wondering if this ought to extend RuntimeException instead. On the one hand, it's nice to provide callers something specific to catch instead of plain old Exception; on the other hand, it depends if you really consider a low-level network problem of the type encountered by the connect methods to really be recoverable. I feel like RuntimeExceptions strike a slightly better balance of "Catch it if you want to be robust, let it fly if you want things to blow up loudly."

 - *Finally* changed getName()'s visibility to public...
 - Fixed a comment on the constructor to say SearchBy instead of SearchLimiter. Must've been an old name.
pom.xml:
 - Added dependency for xmlrpc-client.
Bugzilla.java:
 - Removed throws declarations of ConnectionException from all methods, since...
ConnectionException.java:
 - ... now extends RuntimeException.
Bugzilla.java:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants