[
https://issues.apache.org/jira/browse/SLING-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-633.
------------------------------------
Resolution: Fixed
Fix Version/s: Engine 2.1.0
Added support for the empty string in revisions 881783 and 881785 together with
a simple unit test.
> RequestDispatcherOptions.setReplaceSelectors("") doesn't work
> -------------------------------------------------------------
>
> Key: SLING-633
> URL: https://issues.apache.org/jira/browse/SLING-633
> Project: Sling
> Issue Type: Bug
> Components: Engine
> Environment: org.apache.sling.engine from revision 685501
> Reporter: Jukka Zitting
> Assignee: Carsten Ziegeler
> Priority: Minor
> Fix For: Engine 2.1.0
>
>
> As discussed on the mailing list (see
> http://markmail.org/message/fphyjdeb2oecjqdn), there is an issue when using
> the RequestDispatcher to include other components when the including
> component is addressed with a selector and the included component is not.
> Using the following code doesn't work as expected, the original
> (selector-dispatched) servlet is still invoked for the included resource:
> RequestDispatcherOptions options = new RequestDispatcherOptions();
> options.setReplaceSelectors("");
> RequestDispatcher dispatcher =
> request.getRequestDispatcher(path, options);
> Could it be that an empty replacement string is treated as non-existent?
> Strangely enough the following code works, even though when addressing the
> resource directly in my browser, I get the same result with or without the
> ".html" suffix:
> RequestDispatcher dispatcher =
> request.getRequestDispatcher(path + ".html");
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
