Return-Path: 
 <archiva-dev-return-60-apmail-maven-archiva-dev-archive=maven.apache.org@maven.apache.org>
Delivered-To: apmail-maven-archiva-dev-archive@locus.apache.org
Received: (qmail 52108 invoked from network); 30 Sep 2006 06:04:45 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 30 Sep 2006 06:04:45 -0000
Received: (qmail 86875 invoked by uid 500); 30 Sep 2006 06:04:44 -0000
Delivered-To: apmail-maven-archiva-dev-archive@maven.apache.org
Received: (qmail 86807 invoked by uid 500); 30 Sep 2006 06:04:44 -0000
Mailing-List: contact archiva-dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:archiva-dev-help@maven.apache.org>
List-Unsubscribe: <mailto:archiva-dev-unsubscribe@maven.apache.org>
List-Post: <mailto:archiva-dev@maven.apache.org>
List-Id: <archiva-dev.maven.apache.org>
Reply-To: archiva-dev@maven.apache.org
Delivered-To: mailing list archiva-dev@maven.apache.org
Received: (qmail 86798 invoked by uid 99); 30 Sep 2006 06:04:44 -0000
Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org)
 (140.211.166.84)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Sep 2006 23:04:44 -0700
Authentication-Results: idunn.apache.osuosl.org
 header.from=flamefew@gmail.com; domainkeys=good
X-ASF-Spam-Status: No, hits=0.5 required=5.0 tests=DNS_FROM_RFC_ABUSE
DomainKey-Status: good
X-DomainKeys: Ecelerity dk_validate implementing
 draft-delany-domainkeys-base-01
Received: from [66.249.82.236] ([66.249.82.236:46130]
 helo=wx-out-0506.google.com)
	by idunn.apache.osuosl.org (ecelerity 2.1.1.8 r(12930)) with ESMTP
	id FF/E3-23383-BF80E154 for <archiva-dev@maven.apache.org>;
 Fri, 29 Sep 2006 23:04:44 -0700
Received: by wx-out-0506.google.com with SMTP id h30so1258199wxd
        for <archiva-dev@maven.apache.org>;
 Fri, 29 Sep 2006 23:04:41 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=jTFGEjOzkY9gZLFBXIvXNrshf0Qqv5Se8IVTJAhHrAOpt0rqqq4Pclp2S30UdfRButMjMNlO7nsqzP+ezN3g7orEI4mPUA47y3yJ4xHsAsjEQndQvfAmUTWwNOjC2cqBXcB4JqQ1UnnBomJqYVeJbiJDHXr74zeJ2YoCUOppSKg=
Received: by 10.90.28.12 with SMTP id b12mr2186890agb;
        Fri, 29 Sep 2006 23:04:41 -0700 (PDT)
Received: by 10.90.87.2 with HTTP; Fri, 29 Sep 2006 23:04:41 -0700 (PDT)
Message-ID: <31cc37360609292304n6f877b46w807ac5d0bf3f4295@mail.gmail.com>
Date: Fri, 29 Sep 2006 23:04:41 -0700
From: "Henri Yandell" <flamefew@gmail.com>
To: archiva-dev@maven.apache.org
Subject: jspf problem
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

I can replicate Daniel's problem with jspf files not being
interpreted. Using a basic tomcat install.

Looking at the source, I see three types of jspf includes. The first
are '<%@ include's, the second are '<c:import's and the last are
xwork-security <result> tags. No idea as to which would be bad, but
thought I'd bring it up.

Hen