You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Brian Ka Sing Li (JIRA)" <ji...@apache.org> on 2019/04/28 16:58:00 UTC
[jira] [Created] (SLING-8377) Sling Dynamic Include - Does not
support empty "include selector" option.
Brian Ka Sing Li created SLING-8377:
---------------------------------------
Summary: Sling Dynamic Include - Does not support empty "include selector" option.
Key: SLING-8377
URL: https://issues.apache.org/jira/browse/SLING-8377
Project: Sling
Issue Type: Bug
Affects Versions: Dynamic Include 3.1.2
Reporter: Brian Ka Sing Li
Attachments: UrlBuilder.java, UrlBuilderTest.java
After testing out Sling Dynamic Include 3.1.2, it seems like setting an option (include-filter.config.selector) to BLANK is not supported.
Scenario:
AEM 6.4.2, after installing Dynamic Include, I will configure the OSGI configuration. With an option of an input field (include-filter.config.selector) set to blank, my rendered page received a double dot notation.
Actual (notice the double dot notation)
{code:java}
${root}/resource/path..html
{code}
Expected
{code:java}
${root}/resource/path.html
{code}
I've also included new unit tests Supporting :
{code:java}
UnsetRequestPathInfoSelector UnsetIncludeSelector{code}
{code:java}
SetRequestPathInfoSelector UnsetIncludeSelector{code}
{code:java}
UnsetRequestPathInfoSelector SetIncludeSelector
{code}
I've created a branch and tried to create a pull request, but I am not authorized to do so. Please see attached files for the solution to this problem.
[^UrlBuilder.java]
[^UrlBuilderTest.java]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)