[jira] [Assigned] (SLING-4315) Sling Mocks, OSGi Mocks & Resource Resolver Mock documentation pages contain typos.

["Stefan Seifert (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-4315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Seifert reassigned SLING-4315:
-------------------------------------

    Assignee: Stefan Seifert

> Sling Mocks, OSGi Mocks & Resource Resolver Mock documentation pages contain typos.
> -----------------------------------------------------------------------------------
>
>                 Key: SLING-4315
>                 URL: https://issues.apache.org/jira/browse/SLING-4315
>             Project: Sling
>          Issue Type: Bug
>          Components: Documentation
>            Reporter: Alberto Almagro
>            Assignee: Stefan Seifert
>            Priority: Trivial
>              Labels: documentation
>
> Found some typos and inconsistencies on Sling Mocks, OSGi Mocks & Resource Resolver Mock documentation pages.
> *Sling Mocks* http://sling.apache.org/documentation/development/sling-mock.html
> {panel:title=AdpaterManager -> AdapterManager}
> *AdpaterManager* implementation for registering adapter factories and resolving adaptions
> The implementation is thread-safe so it can be used in parallel running unit tests
> {panel}
> {panel:title=certian -> certain}
> It is possible to set request data to simulate a *certian* Sling HTTP request
> Additional services like MockModelAdapterFactory and MimeTypeService
> The following features are not supported:
> {panel}
> {panel:title=testcases -> test cases}
> Additional features provided:
> SlingContext JUnit Rule for easily setting up a Sling Mock environment in your JUnit *testcases*
> ContentLoader supports importing JSON...
> {panel}
> {panel:title=ist -> is}
> Depending on the type an underlying JCR repository is used or not, and the data *ist* stored in-memory or in a real repository.
> {panel}
> {panel:title=Junit -> JUnit}
> If you use the SlingContext *Junit* rule this is done automatically for you.
> {panel}
> {panel:title=usig -> using}
> With the ContentLoader it is possible to import a binary file stored in the classpath beneath the unit tests. The data is stored *usig* a nt:file/nt:resource or nt:resource node type.
> {panel}
> *OSGi Mocks* http://sling.apache.org/documentation/development/osgi-mock.html
> {panel:title=lifecyle -> lifecycle}
> Call *lifecyle* methods for activating, deactivating or modifying SCR components
> Service and bundle listener implementation
> {panel}
> *Resource Resolver Mock* http://sling.apache.org/documentation/development/resourceresolver-mock.html
> {panel:title=Mimicks -> Mimics}
> *Mimicks* transactions using via commit()/revert() methods
> OSGi events for adding/changing/removing resources
> {panel}
> {panel:title=qeuryResources -> queryResources}
> Querying with *qeuryResources*/findResources not supported (always returns empty result set)
> Sling Mapping is not supported
> {panel}
> {panel:title=resouce -> resource}
> Resolving *resouce* super types
> {panel}
> Other pages like JCR Mocks http://sling.apache.org/documentation/development/jcr-mock.html are free of typos.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)