Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 44828 invoked from network); 9 Nov 2007 17:04:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Nov 2007 17:04:26 -0000 Received: (qmail 59078 invoked by uid 500); 9 Nov 2007 17:03:59 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 59032 invoked by uid 500); 9 Nov 2007 17:03:59 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 59008 invoked by uid 99); 9 Nov 2007 17:03:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Nov 2007 09:03:59 -0800 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Nov 2007 17:04:10 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 8C0E87141FE for ; Fri, 9 Nov 2007 09:03:50 -0800 (PST) Message-ID: <26200889.1194627830562.JavaMail.jira@brutus> Date: Fri, 9 Nov 2007 09:03:50 -0800 (PST) From: "Rick McGuire (JIRA)" To: dev@geronimo.apache.org Subject: [jira] Created: (GERONIMO-3594) Numerous problems in javamail SearchTerm impl. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Numerous problems in javamail SearchTerm impl. ---------------------------------------------- Key: GERONIMO-3594 URL: https://issues.apache.org/jira/browse/GERONIMO-3594 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: mail Reporter: Rick McGuire Assignee: Rick McGuire There are a number of problems in the javamail SearchTerm classes. The fall into several general categories: 1) Some search terms rely on method calls in the Message class that can return a null result. This leads to null pointer exceptions when performing client-side match operations. 2) A number of classes don't override the equals() method and ensure that the other object is of the correct type. 3) Some equals method implementations don't include all data items in the compare, which can lead to false positives. 4) The hashCode methods don't always include all data items in the hash. In at least one case, an item is included that will create an invalid hash that will violate the hashCode()/equals() general contract. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.