[
https://jira.jboss.org/browse/EMBJOPR-309?page=com.atlassian.jira.plugin....
]
Ian Springer closed EMBJOPR-309.
--------------------------------
Assignee: Ian Springer
Resolution: Rejected
Whether or not an error such as this is returned in the form of of a Configuration-based
result or an exception is determined by the the way each particular operation is
implemented in the plugin. In a case such as this where the plugin's operation impl
throws an exception, displaying the exception in a textarea is the correct behavior for
EmbJopr. Of course, we could potentially display the exception in a prettier
user-friendlier format (collapsible panels, indentation, highlighting of first line in
each cause in the stack trace, etc.).
Better error handling for JMS Topics operations
-----------------------------------------------
Key: EMBJOPR-309
URL:
https://jira.jboss.org/browse/EMBJOPR-309
Project: Embedded Jopr
Issue Type: Bug
Components: Web App/Integration
Affects Versions: 1.4.0
Reporter: Ondrej Žižka
Assignee: Ian Springer
Priority: Minor
Error handling is back to dumping an exception to a textarea?
When I perform the "listMessagesForSubscription" operation on a Topic with
a bogus queue name, I get a stacktrace with root cause
Caused by: java.lang.IllegalArgumentException: No subscriptions with name test
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira