since ‎01-08-2019
‎01-10-2020
tadijam47062732
Level 2
Re: Search Servlet not working - probably dependency issue tadijam47062732 - Adobe Experience Manager
This was solved by the following PR: https://github.com/tadijam64/search-engines-comparison/commit/c4232b48e1ac9fc326870884d00e4960376ef14cBy checking out OSGi Components in the Web Console, I've realised there are configurations that this server is depending on that weren't active automatically. By setting them to the default I've managed to solve this issue.
664
Views
0
Likes
0
Answers
Search Servlet not working - probably dependency issue tadijam47062732 - Adobe Experience Manager
Hi, I've implemented research project on using Jackrabbit Oak Lucene, Apache Solr and Elasticsearch in AEM 6.4 on We Retail project. They are all implemented inside the same project so I could measure their results. You can check this project here: https://github.com/tadijam64/search-engines-comparison However, there is one open issue that I am not able to resolve - https://github.com/tadijam64/search-engines-comparison/issues/48 Search is not working on AEM 6.5 (not sure tho if it is related to...
719
Views
0
Likes
1
Answers and Comments
Re: Elasticsearch third arty dependency in AEM tadijam47062732 - Adobe Experience Manager
@cqsapientu69896 you can see it here - I've manually created elasticsearch as separate OSGi bundles in Eclipse and reuse them in my project. You can check everything here: https://github.com/tadijam64/search-engines-comparison
6491
Views
0
Likes
1
Replies
Re: JSON in datasource not working tadijam47062732 - Adobe Experience Manager
This is the correct answer:{ "selector": "user", "scope": { "groupName": "boots-approver", "declaredOnly": false, } }that "," after the "declaredOnly": false was needed for some reason.
590
Views
0
Likes
0
Answers
JSON in datasource not working tadijam47062732 - Adobe Experience Manager
According to this https://jackrabbit.apache.org/api/2.8/org/apache/jackrabbit/commons/jackrabbit/user/AuthorizableQueryManager.html I've put JSON in my datasource to show me users from one group in the selectbox.This way, all works fine:{ "selector": "user", "scope": { "groupName": "test-approver", } }The problem here is that it includes all users from test-approver group, but not users from groups that are members of "test-approver".There is option in the documentation provided at the beginning...
601
Views
0
Likes
1
Answers and Comments
Re: Using SelectDataSource for dynamic select box with us... tadijam47062732 - Adobe Experience Manager
I added custom dialog to the Dynamic Participant Step inside of the workflow. This dialog is shown to the user later with the option to choose which user from some specific group to choose. This group will be entered as an "argument" to the Dynamic Participant Step of the workflow. Already solved it but your answer is correct so I will mark it that way. Thank you.
582
Views
0
Likes
0
Comments
Using SelectDataSource for dynamic select box with users list tadijam47062732 - Adobe Experience Manager
I am trying to use selectdatasource (https://helpx.adobe.com/experience-manager/6-5/sites/developing/using/reference-materials/granite-ui/api/jcr_root/libs/granite/ui/components/coral/foundation/authorizable/selectdatasource/index.html ) for generating selectbox with list of users from the specific group. This is used inside the workflow as a Dynamic Participant Step. Is there any example of using this in similar use case? Documentation is very thin on this one. Any other idea of implementing th...
595
Views
0
Likes
2
Answers and Comments
Hiding/disabling page properties or tabs by user group tadijam47062732 - Adobe Experience Manager
Is there a way to show/hide page properties or tabs based on the user group?It is also necessary to ensure that hiding or disabling of fields does not cause data to be deleted on submission of the dialog.AEM 6.5, SPA + React
1271
Views
1
Like
2
Answers and Comments
Workaround for AEM SPA image inline editing tadijam47062732 - Adobe Experience Manager
Per Adobe's documentation there are some limitations while working with SPA components. One of those is inline image editing.1. Why is this still not available and when it is planned to be enabled with SPA Components?2. Is there a workaround for this? Some custom implementation or examples?AEM 6.5 + React
534
Views
0
Likes
0
Replies
Re: Elasticsearch third arty dependency in AEM tadijam47062732 - Adobe Experience Manager
No, I run clean install
6550
Views
0
Likes
0
Replies
Re: Elasticsearch third arty dependency in AEM tadijam47062732 - Adobe Experience Manager
Tried that, but many things can not get resolved that way in my case.
6556
Views
0
Likes
3
Replies
Elasticsearch third arty dependency in AEM tadijam47062732 - Adobe Experience Manager
I am having some problems using elasticsearch-rest-high-level-client dependency in my project.According to Elasticsearch documentation only this should be included: org.elasticsearch.client elasticsearch-rest-high-level-client 7.4.0However, there were many NoClassDefinitionFound errors, so I embed the package inside maven-bundle-plugin. I realized that no transitive dependencies are included (altho I have true)so I've added many of them like this: org.apache.felix maven-bundle-plugin true org....
6742
Views
0
Likes
7
Replies
Re: Using Elasticsearch Rest High Client problem in AEM tadijam47062732 - Adobe Experience Manager
So my guess was right, transitive dependencies were not included altho Transitive>true exists.The following is necessary when running elasticsearch as search engine on AEM the problem: org.elasticsearch.client elasticsearch-rest-high-level-client org.elasticsearch.client elasticsearch-rest-client org.elasticsearch elasticsearch org.elasticsearch elasticsearch-x-content org.elasticsearch.plugin rank-eval-client org.apache.commons commons-imaging test org.elasticsearch.plugin lang-mus...
1369
Views
0
Likes
0
Answers
Re: AEM - Maven build cannot resolve dependencies when imported tadijam47062732 - Adobe Experience Manager
Jackson dependencies are part of OSGi and should not be added as embed dependency. Please, correct me if I am wrong.I had a similar problem and figure out that there is already imported jackson dependency in intelliJ and I was overriding it with added jackson version.Please check External Dependencies in your IDE:Please make sure that all of those are defined with the same version. In my case, I have changed all jackson dependencies in pom.xml on 2.8.11 and it all worked fine without embedding.
2167
Views
0
Likes
0
Answers
Re: Using Elasticsearch Rest High Client problem in AEM tadijam47062732 - Adobe Experience Manager
Thank you for the effort, but it does not work in my case. Forbidding importing of packages that I am going to use should not fix the issue.I can not add an "elasticsearch" artifactId in because then build fails.Can you please try to clone my repo and try to make your changes, because I had no success in doing so?GitHub - tadijam64/search-engines-comparison-on-we-retail at elasticsearch_servlet_impl The idea is to access some page (for example http://localhost:4902/editor.html/content/we-retail...
1421
Views
0
Likes
0
Answers
Re: Using Elasticsearch Rest High Client problem in AEM tadijam47062732 - Adobe Experience Manager
If I do it this way: org.apache.felix maven-bundle-plugin true bundle-manifest process-classes manifest artifactId1, artifactId2;inline=true --> org.apache.servicemix.bundles.solr-solrj, log4j, noggit, zookeeper, elasticsearch-rest-client, elasticsearch-rest-high-level-client, org.apache.servicemix.bundles.elasticsearch, elasticsearch; inline=true false OSGI-INF/lib we.retail.core.model* *;resolution:=optional, org.elasticsearch;version=7.4.0,* we.retail.core* we.retail.core.model Then I am not able to build the project ...
1350
Views
0
Likes
0
Answers
Using Elasticsearch Rest High Client problem in AEM tadijam47062732 - Adobe Experience Manager
I am trying to use Java High Level Rest Client in Adobe Experience Manager to finish project of comparisson between Lucene, Solr and Elasticsearch search engines.I am having some problems with dependencies that I don't understand so any info on this would be valid.Here is the code:Dependencies in the parent pom.xml (the same are defined in core pom.xml): org.elasticsearch elasticsearch 7.4.0 org.elasticsearch.client elasticsearch-rest-client 7.4.0 org.elasticsearch.client elasticsearch-rest-high...
2389
Views
1
Like
6
Answers and Comments
Re: Indexing data - Indexing Rules tadijam47062732 - Adobe Experience Manager
Does that mean that without these properties defined, these indexes would be indexed?if the structure is like this:- lucene - aggregates (nt:file) - indexRules - nt:base - properties (nothing inside)Would then everything that is (or extends) nt:file be indexed (every single property)?I am not sure if some property is indexed without being defined inside indexRules/properties, or it is OOTB behaviour and then if we want custom behaviour for some properties, we define them inside indexRules only t...
713
Views
0
Likes
0
Answers
Indexing data - Indexing Rules tadijam47062732 - Adobe Experience Manager
Per Lucene documentation, the following is definition of Indexing Rules on oak indexes inside AEM:Indexing rules defines which types of node and properties are indexed. An index configuration can define one or more indexingRules for different nodeTypes.However, when I check on indexes created in We Retail project, I can see that there are nodes like this:/oak:index/lucene/indexRules/nt:base/properties/childrenOrderThere is lucene index with many properties inside indexRules node. Every property ...
1404
Views
2
Likes
4
Answers and Comments
Re: We retail - Traversal index tadijam47062732 - Adobe Experience Manager
It makes sense, I just thought it should run "infinity cost" if there is no cost lower than that. I will mark your question as correct. Thank you
748
Views
0
Likes
0
Answers
Re: We retail - Traversal index tadijam47062732 - Adobe Experience Manager
I have the same situation, now I am interested why it does not return any nodes as search results?And how could I achieve that?Because speed of traversal search that does not find any node is 1ms so it can not be compared to lucene index when lucene actually goes through content and searches nodes (which takes more time)
678
Views
0
Likes
0
Answers
Re: We retail - Traversal index tadijam47062732 - Adobe Experience Manager
I set property type=disabled on lucene index node under oak:index
658
Views
0
Likes
0
Answers
Re: We retail - Traversal index tadijam47062732 - Adobe Experience Manager
Yes
658
Views
0
Likes
0
Answers
Re: We retail - Traversal index tadijam47062732 - Adobe Experience Manager
That is exactly what I need. I am doing research on how much improvement will lucene index bring.I want to run query with traversal (and get results) and then do the same with lucene index included.So no business case, just research.
677
Views
0
Likes
0
Answers
We retail - Traversal index tadijam47062732 - Adobe Experience Manager
I am trying to make AEM search to search for "sonja" jacket with traversal node to see how much time it will need.I disabled lucene and cqPageLucene indexes from oak:index, but can not find any nodes when trying this query in Explain Query tool:/jcr:root/content/we-retail/us/en//element(*, cq:Page)[(jcr:contains(., 'sonja'))]This is tested on We Retail project.Why this does not find any nodes, and with indexes it does?What will be needed for this to find pages that have "sonja" in their title? (...
2277
Views
1
Like
11
Answers and Comments
Why is We Retail deprecated (achieved) tadijam47062732 - Adobe Experience Manager
On (Adobe We Retail)[GitHub - Adobe-Marketing-Cloud/aem-sample-we-retail: We.Retail has been archived, see instead the WKND Guide:​ ] - reference project site it said:"We.Retail is no longer supported, the WKND Guide is the replacement reference site for Adobe Experience Manager."Does anyone knows why is this the case?https://github.com/Adobe-Marketing-Cloud/aem-sample-we-retail#modules
637
Views
1
Like
2
Answers and Comments
Re: Why are some page properties disabled on AEM We Retail reference site tadijam47062732 - Adobe Experience Manager
JaideepBrar​ yes, but does that mean that on the path http://server:port/sites.html/content/we-retail/language-masters/en/products there should be no inheritance? Because I can see that these properties are disabled there as well.
609
Views
0
Likes
0
Answers
Why are some page properties disabled on AEM We Retail reference site tadijam47062732 - Adobe Experience Manager
I am doing some search-engines related research on Adobe Experience Manager's reference site - We Retail.I've realised that page properties on some pages (ex. http://server:port/sites.html/content/we-retail/us/en/products) are disabled like it is shown in this picture. Tried on another clean instance, it is the same.What could be a reason for this and where it can be enabled for editing again?The interesting fact is that I can edit the same page properties in page -> page information -> edit tem...
775
Views
1
Like
3
Answers and Comments