Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <15691526.1200595834049.JavaMail.jira@brutus>
Date: Thu, 17 Jan 2008 10:50:34 -0800 (PST)
From: "Drew Buschhorn (JIRA)" <jira@apache.org>
To: dev@cocoon.apache.org
Subject: [jira] Commented: (COCOON-2162) [PATCH] Fix for Paginator when
 accessing out of bounds Pagination page
In-Reply-To: <2656369.1200418175255.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/COCOON-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560029#action_12560029 ] 

Drew Buschhorn commented on COCOON-2162:
----------------------------------------

That would be a great idea, but unfortunately I dont know how to throw that in cocoon.  If you'd like to make the mod or can point me in the right direction (is it in the avalon framework, maybe?) I'd be happy to take a look at it.

http://www.jdocs.com/page/LibraryContents?id=4&c=X
List of cocoon exceptions that I could find.

> [PATCH] Fix for Paginator when accessing out of bounds Pagination page
> ----------------------------------------------------------------------
>
>                 Key: COCOON-2162
>                 URL: https://issues.apache.org/jira/browse/COCOON-2162
>             Project: Cocoon
>          Issue Type: Improvement
>          Components: Blocks: (Undefined)
>    Affects Versions: 2.1.10, 2.1.11
>            Reporter: Drew Buschhorn
>            Priority: Minor
>         Attachments: paginator.diff, screenshot-1.jpg
>
>
> The Paginator transformer for apache cocoon will allow out of page-range requests.
> I've added the below logic-test into my own copy of cocoon, and that seems to fix the problem.
> Please let me know if you think 1. this is valid and 2. that it should be placed into svn for the 2.1.x version of cocoon.
> Example:
> http://localhost/samples/paginator/text(5)
> will return a valid empty file before patch (despite there being only 4 pages worth of data to paginate)
> after patch, returns ResourceNotFound/404.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.