Did you look at the DataSource examples?

Hi,It looks like there needs to be an additional mixin which allows the sling:basename property on nt:file nodes. You can create your own mixin to do that, but please also file a DayCare ticket so this gets addressed in the product.Regards,Justin

Hi,As Scott wrote above and as is documented a few times on https://docs.adobe.com/docs/en/aem/6-1/administer/ecommerce/concepts.html, the JCR commerce implementation is for demo and instructional purposes. It is not intended to be used in production. In your particular case, you could use it as a b...

Hi,I assume you are referring to https://docs.adobe.com/docs/en/aem/6-0/develop/ref/javadoc/com/adobe/granite/resourceresolverhelper/ResourceResolverHelper.html. If so, this really only works in a request context in which case it will be the ResourceResolver associated with the current request.So:1)...

Hi,That package is not exported so you cannot use it. If you want to read the configuration values, I'd suggest using the OSGi Configuration Admin service.Regards,Justin

The Azure Blob Storage (which is the equivelant of S3) as a DataStore is not suppported. If you run on Azure, you have to use Azure File Storage and the FileDataStore. You could theoretically create your own DataStore implementation on top of Azure Blob Storage, but this would obviously not be suppo...

Hi,It depends upon how the query is formulated. If you run a full-text search (i.e. using the contains operator), then all keywords are searched, which in this case includes all of the path segements of the tagId. If you run a property search on the cq:tags property, then the exact property value wo...

Hi,When using MSRP, Solr is used for searching for user-generated content stored in MongoDB. This search is handled by MSRP and isn't something you would directly interact with. Right now, only Solr is supported with MSRP.Regards,Justin

To be clear, there should be a space between the search term and the "order" bit.But assuming you're doing that, I don't know why that wouldn't be working. You can try turning on debug logging for the logger org.apache.jackrabbit.core.query. This should allow you to see the translated XPath query.

Hi,This does not require reconfiguring Lucene. All you need to do is modify the Content Finder tab (/libs/wcm/extensions/contentfinder/images.js in this case). Specifically, what you would do is modify the JavaScript to add "order:jcr:content/metadata/dc:title" to the submitted query term. You can a...