[
https://issues.apache.org/jira/browse/CASSANDRA-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499597#comment-13499597
]
Dave Brosius commented on CASSANDRA-4893:
-----------------------------------------
doesn't doing
throw new IllegalArgumentException(e);
still exhibit the problem of needing the underlying exception class of 'e' in
the classpath of the caller?
why not just catch the exception in the MBean itself, and throw an alternative
there, so as not to soften the exception handling in the main codebase?
> Don't throw internal exceptions over JMX
> ----------------------------------------
>
> Key: CASSANDRA-4893
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4893
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.6, 1.2.0 beta 1
> Reporter: Nick Bailey
> Assignee: Yuki Morishita
> Fix For: 1.2.1
>
> Attachments:
> 0001-remove-cassandra-specific-exceptions-from-JMX-interf.patch
>
>
> Similarly to how we don't return internal objects over JMX we shouldn't throw
> internal exceptions over jmx as well.
> The one example I encountered was throwing ConfigurationException for the
> move() command. We should check the rest of our jmx as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
