[
https://issues.apache.org/jira/browse/SLING-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Janandith Uditha Jayawardena updated SLING-475:
-----------------------------------------------
Attachment: JSPSlingIncludeTest.patch
Hi,
This is the completed patch for SLING-475 integration test.
This has 9 tests.
one is a test without <sling:include /> used to see whether contents of a node
are rendered by a script.
8 others test parameters of <sling:include /> tag.
These are path , resource , resourceType , addSelectors , replaceSelectors ,
flush and replaceSuffix.
The last test called testCustomScriptInput was added because it was desired to
test sling:include by adding the specific string with sling:include to an
existing skeleton.
This is an effort to implement the feature suggested here
https://issues.apache.org/jira/browse/SLING-475?focusedCommentId=12621443#action_12621443
I have a doubt whether this is the actual behavior expected. It's what I
understood :-). Please feel free to comment. I can improve this based on your
feedback.
Thanks a lot for helping me solve questions which came across when
implementing these integration tests. I'm so grateful for all the support given
by sling dev
Janandith.
> Create Integration tests for the sling:include tag
> --------------------------------------------------
>
> Key: SLING-475
> URL: https://issues.apache.org/jira/browse/SLING-475
> Project: Sling
> Issue Type: Sub-task
> Components: Scripting JSP
> Reporter: Felix Meschberger
> Attachments: JSPSlingIncludeTest.patch, PatchWithError.patch,
> SLING-475.patch, sling475.patch, sling475.patch, sling475.patch,
> Sling475_simple_patch.patch, working.patch
>
>
> Summary says it all ;-)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
