Return-Path: X-Original-To: apmail-directory-dev-archive@www.apache.org Delivered-To: apmail-directory-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A6028E3DE for ; Mon, 4 Feb 2013 02:30:13 +0000 (UTC) Received: (qmail 81955 invoked by uid 500); 4 Feb 2013 02:30:13 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 81751 invoked by uid 500); 4 Feb 2013 02:30:12 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 81739 invoked by uid 99); 4 Feb 2013 02:30:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Feb 2013 02:30:12 +0000 Date: Mon, 4 Feb 2013 02:30:12 +0000 (UTC) From: "Emmanuel Lecharny (JIRA)" To: dev@directory.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (DIRAPI-119) Soem NPE when sendning some request with lacking data MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Emmanuel Lecharny created DIRAPI-119: ---------------------------------------- Summary: Soem NPE when sendning some request with lacking data Key: DIRAPI-119 URL: https://issues.apache.org/jira/browse/DIRAPI-119 Project: Directory Client API Issue Type: Bug Reporter: Emmanuel Lecharny Priority: Critical Sending a request, like a ModifyRequest, with some missing data like the DN will leads to some NPE inside the encoder, which will translates to some cryptic error being returned by the server : org.apache.directory.api.ldap.model.exception.LdapException: PROTOCOL_ERROR: The server will disconnect! We need to return a decent error, and also avoid any NPE. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira