Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 94429200D11 for ; Mon, 2 Oct 2017 19:34:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 92AC31609C0; Mon, 2 Oct 2017 17:34:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id E19881609EF for ; Mon, 2 Oct 2017 19:34:03 +0200 (CEST) Received: (qmail 7095 invoked by uid 500); 2 Oct 2017 17:34:02 -0000 Mailing-List: contact dev-help@sling.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@sling.apache.org Delivered-To: mailing list dev@sling.apache.org Received: (qmail 7074 invoked by uid 99); 2 Oct 2017 17:34:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Oct 2017 17:34:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id E7A9C1A5D2E for ; Mon, 2 Oct 2017 17:34:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id x6Rkpo0qZM5n for ; Mon, 2 Oct 2017 17:34:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 255EE610D0 for ; Mon, 2 Oct 2017 17:34:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 9B865E059C for ; Mon, 2 Oct 2017 17:34:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 4EE6A242B7 for ; Mon, 2 Oct 2017 17:34:00 +0000 (UTC) Date: Mon, 2 Oct 2017 17:34:00 +0000 (UTC) From: "Justin Edelson (JIRA)" To: dev@sling.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SLING-7174) Using MockSlingHttpServletRequest for In-Sling Rendering fails when used with Export Servlet MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 02 Oct 2017 17:34:04 -0000 [ https://issues.apache.org/jira/browse/SLING-7174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16188477#comment-16188477 ] Justin Edelson commented on SLING-7174: --------------------------------------- bq. If that Request / Response pair if for In-Sling rendering why is it then prefixed with 'Mock' Because naming things is hard. bq. why does it throw an Unsupported Operation Exception? Presumably because no one thought that was an issue. > Using MockSlingHttpServletRequest for In-Sling Rendering fails when used with Export Servlet > -------------------------------------------------------------------------------------------- > > Key: SLING-7174 > URL: https://issues.apache.org/jira/browse/SLING-7174 > Project: Sling > Issue Type: Bug > Components: Extensions > Environment: Sling 9, Java 1.8 > Reporter: Andreas Schaefer > Assignee: Justin Edelson > > When I use MockSlingHttpServletRequest with SlingRequestProcessor to render a page within sling then I will get an Unsupported Operation Exception when I hit the Export Servlet. > The reason is that the Export Servlet is retrieving Request Reader in addScriptBindings(): > bindings.put(READER, request.getReader()); > In my opinion Sling should provide a Request / Response class for in-Sling rendering that is for that specific purpose as using that class for testing does clash with the the rendering. -- This message was sent by Atlassian JIRA (v6.4.14#64029)