Return-Path: Delivered-To: apmail-incubator-esme-dev-archive@minotaur.apache.org Received: (qmail 30238 invoked from network); 3 Jan 2010 15:53:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Jan 2010 15:53:27 -0000 Received: (qmail 8960 invoked by uid 500); 3 Jan 2010 15:53:27 -0000 Delivered-To: apmail-incubator-esme-dev-archive@incubator.apache.org Received: (qmail 8904 invoked by uid 500); 3 Jan 2010 15:53:26 -0000 Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: esme-dev@incubator.apache.org Delivered-To: mailing list esme-dev@incubator.apache.org Received: (qmail 8894 invoked by uid 99); 3 Jan 2010 15:53:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 03 Jan 2010 15:53:26 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of esjewett@gmail.com designates 209.85.160.41 as permitted sender) Received: from [209.85.160.41] (HELO mail-pw0-f41.google.com) (209.85.160.41) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 03 Jan 2010 15:53:19 +0000 Received: by pwj4 with SMTP id 4so1171755pwj.20 for ; Sun, 03 Jan 2010 07:52:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=tu02OvV1WbnLw0k+8zIBF4MV9DKxoX7bndIB3pNEjfY=; b=uYKkpGqfX5qYsOxB0+SBgHEXataiHdxrDoQRD2IG6rAwh/bsjcYBm8nn8NrHtBsbRb VWonMH8yymuX7syWviBQFfWzRYLTk3etNHDrLzv8avsiHQP3+qHlD1jYWbR+5+TElZb/ c0Zwfzsp12/Ml9vPqJtsxrvaHUWEUnqGrzNhY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=A9qY6M/FQOdKQ/yo5X29zyHcyfA4GDOLn+orf0b9ko2Y27/tCNG6bZOylPaPbaOdaj GiyFydwrgo1ihYSjJ+MJxFgrYCItuzAXAwlAL5C8aGBHDVwTnbKxfYaTsNO67qmsX5B7 apDlkwhmeHKy7uET/jnmeZKCdS1gPy5wmyfzw= MIME-Version: 1.0 Received: by 10.141.91.17 with SMTP id t17mr15663961rvl.245.1262533979206; Sun, 03 Jan 2010 07:52:59 -0800 (PST) Date: Sun, 3 Jan 2010 09:52:59 -0600 Message-ID: <68f4a0e81001030752g34ddd6wf64290ddd9226e93@mail.gmail.com> Subject: Posting message to pool strips tags - Bug? From: Ethan Jewett To: esme-dev Content-Type: text/plain; charset=ISO-8859-1 Hi, I've got Jira issue 151 (https://issues.apache.org/jira/browse/ESME-151) created because Sig (Thingamy) is reporting issues posting messages to pools. Specifically, tags are stripped when posting to a pool. The reason is little code snippet in the UserActor.scala file: val tagLst = pool match { case Empty => tags.removeDuplicates.map(Tag.findOrCreate) case _ => Nil } It removes tags when a message is posted to a pool. Is there here for a reason? Is there a security reason? It's definitely something we need to fix, but I want to be sure that I'm not exposing messages in a pool through the tag UI. I think I will go ahead and fix this so that Sig can continue, but if there is something else that needs to be adjusted, please let me know and I'll work on that as well. Thanks, Ethan