You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if the concrete implementation doesn't explicitly throw a JMSException, it does not need to be declared as part of the method signature. for example, SQSMessageConsumer.setMessageListener does not need to declare this exception.
i have a desire to use this implementation and i'm ok w/ using the SQS* classes directly (i'm wrapping them in other code). not having to deal w/ these exceptions when they aren't actually thrown would be helpful and help simplify the underlying code.
there also seems to be inconsistency in how RuntimeException subclasses are handled. in some cases, they are re-wrapped and re-thrown as JMSExceptions (bleh). in other cases, they are not.
The text was updated successfully, but these errors were encountered:
if the concrete implementation doesn't explicitly throw a
JMSException
, it does not need to be declared as part of the method signature. for example,SQSMessageConsumer.setMessageListener
does not need to declare this exception.i have a desire to use this implementation and i'm ok w/ using the
SQS*
classes directly (i'm wrapping them in other code). not having to deal w/ these exceptions when they aren't actually thrown would be helpful and help simplify the underlying code.there also seems to be inconsistency in how
RuntimeException
subclasses are handled. in some cases, they are re-wrapped and re-thrown asJMSException
s (bleh). in other cases, they are not.The text was updated successfully, but these errors were encountered: