Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 79501200CDD for ; Mon, 7 Aug 2017 16:53:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 77CC316570D; Mon, 7 Aug 2017 14:53:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id BE118165709 for ; Mon, 7 Aug 2017 16:53:08 +0200 (CEST) Received: (qmail 10968 invoked by uid 500); 7 Aug 2017 14:53:08 -0000 Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list issues@activemq.apache.org Received: (qmail 10959 invoked by uid 99); 7 Aug 2017 14:53:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Aug 2017 14:53:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 6A5A4C0386 for ; Mon, 7 Aug 2017 14:53:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 9Rk3RBvsQEV8 for ; Mon, 7 Aug 2017 14:53:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id C37A860DB8 for ; Mon, 7 Aug 2017 14:53:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id C8120E0D39 for ; Mon, 7 Aug 2017 14:53:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 255E824161 for ; Mon, 7 Aug 2017 14:53:00 +0000 (UTC) Date: Mon, 7 Aug 2017 14:53:00 +0000 (UTC) From: "Christopher L. Shannon (JIRA)" To: issues@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ARTEMIS-1327) Support checked exceptions from ActiveMQServerPlugin MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 07 Aug 2017 14:53:09 -0000 [ https://issues.apache.org/jira/browse/ARTEMIS-1327?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated ARTEMIS-1327: -------------------------------------------- Description: After I was writing a couple custom plugins I realized it = would be beneficial to support checked exceptions. This makes error handli= ng simpler for plugin writers as they can throw various exceptions and not = have to always wrap them in a RuntimeException. Almost every place in the = broker where plugin methods are currently called already support handling c= hecked Exceptions so this is pretty simple and mostly we just need to add a= "throws Exception" to each of the methods in the ActiveMQServerPlugin inte= rface and make sure the methods used to execute the plugin methods also sup= port it. (was: After I was writing a couple custom plugins I realized it w= ould be beneficial to support checked exceptions. This makes error handlin= g simpler for plugin writers as they can throw various exceptions and not h= ave to always wrap them in a RuntimeException. Almost every place in the b= roker where plugin methods are currently called already support handling ch= ecked Exceptions so this is pretty simply and mostly just need to add a "th= rows Exception" to each of the methods in the ActiveMQServerPlugin interfac= e and make sure the methods used to execute the plugin methods also support= it.) > Support checked exceptions from ActiveMQServerPlugin > ---------------------------------------------------- > > Key: ARTEMIS-1327 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1327 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker > Reporter: Christopher L. Shannon > Assignee: Christopher L. Shannon > Fix For: 2.3.0 > > > After I was writing a couple custom plugins I realized it would be benefi= cial to support checked exceptions. This makes error handling simpler for = plugin writers as they can throw various exceptions and not have to always = wrap them in a RuntimeException. Almost every place in the broker where pl= ugin methods are currently called already support handling checked Exceptio= ns so this is pretty simple and mostly we just need to add a "throws Except= ion" to each of the methods in the ActiveMQServerPlugin interface and make = sure the methods used to execute the plugin methods also support it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)