Return-Path: Delivered-To: apmail-incubator-esme-dev-archive@minotaur.apache.org Received: (qmail 72881 invoked from network); 5 Oct 2009 12:45:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 5 Oct 2009 12:45:00 -0000 Received: (qmail 53827 invoked by uid 500); 5 Oct 2009 12:45:00 -0000 Delivered-To: apmail-incubator-esme-dev-archive@incubator.apache.org Received: (qmail 53793 invoked by uid 500); 5 Oct 2009 12:45:00 -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 53783 invoked by uid 99); 5 Oct 2009 12:45:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Oct 2009 12:45:00 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of vdichev@gmail.com designates 209.85.218.226 as permitted sender) Received: from [209.85.218.226] (HELO mail-bw0-f226.google.com) (209.85.218.226) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Oct 2009 12:44:51 +0000 Received: by bwz26 with SMTP id 26so2281326bwz.12 for ; Mon, 05 Oct 2009 05:43:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=sKAkLKmS1E7n+50kCbNElGIYTYpC7BahugPeELYWY2U=; b=hwaXjh5F59Fd4IW6+kGeNi8nt+GaXLBFE1cZG8n+RQbuCj66a/+CAaBbrpK7ffQNaG aoiCyW3n63RP04sMC1bOmEwe2BYLmay0j1W1WBFIJGFHf/LPLOuUICwwO2E4aVxc/fHj ew6FkpJTqrtwX4QiFYEKnJenajHVkFMKS05IM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=FqG3yfIfHjC8jdjNkmU0YK/d/rDeJSo+1z/DdDwSbRFiQieNjRsZYVr1t3Katz4t7q HnIfPIAedaEQaVCWWMWFYnGbRJHn86f+oOWtZV98wkBnX8bejVpbmVMEXYSh4nyGQZ2A eaQyykVUFuIDftChFGJbSVjRRU3dkx9f9dPuw= MIME-Version: 1.0 Sender: vdichev@gmail.com Received: by 10.204.7.195 with SMTP id e3mr3908099bke.118.1254746611224; Mon, 05 Oct 2009 05:43:31 -0700 (PDT) In-Reply-To: References: <8B4085A3-9642-4661-A3B4-4C6E7767D456@davebsoft.com> <461BFE37-FF54-4BA0-B5D9-B40BF4515500@gmail.com> Date: Mon, 5 Oct 2009 15:43:31 +0300 X-Google-Sender-Auth: 80fea75be601bb21 Message-ID: Subject: Re: New Jira item for user list page From: Vassil Dichev To: esme-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Yes, it's not because of the user properties, but because of a message I've sent on purpose to check if a bug I'm trying to analyze exists on the stax deployment, too. The message is appropriately called "Boom" :) For some reason the textile formatter doesn't play well with LiftSession processing. The message in question is eventually formatted in the following fashion:

Boom

\u000a
\u000a The \u000a character is the newline character and should be treated as whitespace, so this shouldn't matter, but who knows... Note: if you resend this message, this will also crash the regular timeline... Sorry about this unpleasant surprise, now trying to debug the issue. Vassil