Author: sseifert
Date: Fri Oct 14 22:24:50 2016
New Revision: 1764991

URL: http://svn.apache.org/viewvc?rev=1764991&view=rev
Log:
SLING-6157 Context-Aware Config: Change java package name to o.a.s.caconfig

Modified:
    
sling/site/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration-spi.mdtext
    
sling/site/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration.mdtext

Modified: 
sling/site/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration-spi.mdtext
URL: 
http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration-spi.mdtext?rev=1764991&r1=1764990&r2=1764991&view=diff
==============================================================================
--- 
sling/site/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration-spi.mdtext
 (original)
+++ 
sling/site/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration-spi.mdtext
 Fri Oct 14 22:24:50 2016
@@ -24,23 +24,23 @@ All existing implementations are iterate
 
 # Context Path Strategy
 
-By providing an implementation of 
`org.apache.sling.contextaware.config.resource.spi.ContextPathStrategy` you can 
provide additional ways how context paths and their configuration references 
are detected in your content resource hierarchy.
+By providing an implementation of 
`org.apache.sling.caconfig.resource.spi.ContextPathStrategy` you can provide 
additional ways how context paths and their configuration references are 
detected in your content resource hierarchy.
 
 E.g. you could implement detecting context paths by project-specific 
conventions.
 
 
 # Configuration Resource Resolver Strategy
 
-By providing an implementation of 
`org.apache.sling.contextaware.config.resource.spi.ConfigurationResourceResolvingStrategy`
 you can define where configuration data is looked up, and how resource and 
property inheritance is handled.
+By providing an implementation of 
`org.apache.sling.caconfig.resource.spi.ConfigurationResourceResolvingStrategy` 
you can define where configuration data is looked up, and how resource and 
property inheritance is handled.
 
 
 # Configuration Persistence Strategy
 
-By providing an implementation of 
`org.apache.sling.contextaware.config.spi.ConfigurationPersistenceStrategy` you 
can define the peristence structure of the configuration within the 
configuration resources.
+By providing an implementation of 
`org.apache.sling.caconfig.spi.ConfigurationPersistenceStrategy` you can define 
the peristence structure of the configuration within the configuration 
resources.
 
 E.g. you could use a specific JCR node type or slightly different content 
structure to store the configuration data.
 
 
 # Configuration Metadata Provider
 
-By providing an implementation of 
`org.apache.sling.contextaware.config.spi.ConfigurationMetadataProvider` you 
can provide information about configuration metadata from other sources than 
annotation classes.
+By providing an implementation of 
`org.apache.sling.caconfig.spi.ConfigurationMetadataProvider` you can provide 
information about configuration metadata from other sources than annotation 
classes.

Modified: 
sling/site/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration.mdtext
URL: 
http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration.mdtext?rev=1764991&r1=1764990&r2=1764991&view=diff
==============================================================================
--- 
sling/site/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration.mdtext
 (original)
+++ 
sling/site/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration.mdtext
 Fri Oct 14 22:24:50 2016
@@ -36,7 +36,7 @@ The service for getting the configuratio
 - getting all child resources of a named configuration resource.
 
 For example to get a configuration resource for a content resource at 
/content/mysite/page1, you would get a reference to the OSGi service
-`org.apache.sling.contextaware.config.resource.ConfigurationResourceResolver` 
and write:
+`org.apache.sling.caconfig.resource.ConfigurationResourceResolver` and write:
 
     #!java
     Resource contentResource = 
resourceResolver.getResource("/content/mysite/page1");
@@ -62,7 +62,7 @@ and the context-aware configuration supp
 
 Context-aware configurations are built on top of context-aware resources. The 
same concept is used: configurations are
 named and the service to get them is the ConfigurationResolver. You can get a 
reference to the OSGi service
-`org.apache.sling.contextaware.config.ConfigurationResolver` - it has a single 
method to get a ConfigurationBuilder.
+`org.apache.sling.caconfig.ConfigurationResolver` - it has a single method to 
get a ConfigurationBuilder.
 Alternatively you can directly adapt your content resource directly to the 
ConfigurationBuilder interface and get the configuration:
 
     #!java
@@ -140,13 +140,13 @@ Example configuration:
         <configuration>
             <instructions>
                 <!-- Generate bundle header containing all configuration 
annotation classes -->
-                
<_plugin>org.apache.sling.contextaware.config.bndplugin.ConfigurationClassScannerPlugin</_plugin>
+                
<_plugin>org.apache.sling.caconfig.bndplugin.ConfigurationClassScannerPlugin</_plugin>
             </instructions>
         </configuration>
         <dependencies>
             <dependency>
                 <groupId>org.apache.sling</groupId>
-                
<artifactId>org.apache.sling.contextaware.config.bnd-plugin</artifactId>
+                <artifactId>org.apache.sling.caconfig.bnd-plugin</artifactId>
                 <version>1.0.0</version>
             </dependency>
         </dependencies>


Reply via email to