Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F2F04E2D0 for ; Tue, 29 Jan 2013 14:53:53 +0000 (UTC) Received: (qmail 13951 invoked by uid 500); 29 Jan 2013 14:53:53 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 13578 invoked by uid 500); 29 Jan 2013 14:53:52 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 13549 invoked by uid 99); 29 Jan 2013 14:53:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Jan 2013 14:53:51 +0000 X-ASF-Spam-Status: No, hits=0.9 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of tabish121@gmail.com designates 209.85.216.48 as permitted sender) Received: from [209.85.216.48] (HELO mail-qa0-f48.google.com) (209.85.216.48) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Jan 2013 14:53:45 +0000 Received: by mail-qa0-f48.google.com with SMTP id j8so337447qah.7 for ; Tue, 29 Jan 2013 06:53:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:subject:from:to:date:in-reply-to:references :content-type:x-mailer:mime-version:content-transfer-encoding; bh=3GTsD5/WJc80N+9anO2NdOgt6I0uZSpBkOIGdnYYdyg=; b=CU3AqJikfcRg8CnpxAVAsdrkjXJnGREfZSXbBvTwee2sqBl8AtWnewdE2/uTi4xdrZ 1Dqn2nQ7ROVKMe2tAWtdFrY2BcPaEqgPLjHjwlrb9q/mLPNb4AWuqUEWWkHM9GgCLDbY RHn4M4qbZYAlgDxc2673nCRkt89ZnzdH9LGXw1e91Eolyhsz9DeFQwMHEJ7yoldVvDYm h15RXtGBchhXTqwy3HqlRsZorxxEMFAncT40XXD5DbELF58YBUhT9pKmRj6EOpk3qYtp PHnSYVWwfbwq2hWIRNrFOUMWrYT1whiMBfjt4/eQ+P9y8ojSC/IxukaFv6Uu3+QwBbhL 9OJg== X-Received: by 10.49.71.204 with SMTP id x12mr1439054qeu.47.1359471204086; Tue, 29 Jan 2013 06:53:24 -0800 (PST) Received: from [192.168.2.150] (c-98-231-181-148.hsd1.va.comcast.net. [98.231.181.148]) by mx.google.com with ESMTPS id i9sm7700245qei.10.2013.01.29.06.53.22 (version=SSLv3 cipher=RC4-SHA bits=128/128); Tue, 29 Jan 2013 06:53:23 -0800 (PST) Message-ID: <1359471202.2623.1.camel@OfficePC> Subject: Re: Regarding CMS error codes From: Timothy Bish To: users@activemq.apache.org Date: Tue, 29 Jan 2013 09:53:22 -0500 In-Reply-To: <1359467001920-4662391.post@n4.nabble.com> References: <1359374401839-4662309.post@n4.nabble.com> <1359383235.2633.1.camel@OfficePC> <1359467001920-4662391.post@n4.nabble.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.6.0-0ubuntu3 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Tue, 2013-01-29 at 05:43 -0800, Gangadhar Rao wrote: > How do we know the specific exception type what the CMS API is throwing... > > I have looked at the CMS documentation and the API's are returning the > CMSException type....and not the specific CMSSecurityException for > example.... > > So in this case how do we actually get the specific exception type.... In some cases we don't yet have code that can translate from the Java Exception that's marshaled into a corresponding CMS type. In that case its just going to throw a plain CMSException. If you want to contribute to the project we welcome patches. > > > > > -- > View this message in context: http://activemq.2283324.n4.nabble.com/Regarding-CMS-error-codes-tp4662309p4662391.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- Tim Bish Sr Software Engineer | RedHat Inc. tim.bish@redhat.com | www.fusesource.com | www.redhat.com skype: tabish121 | twitter: @tabish121 blog: http://timbish.blogspot.com/