prestonModOp
Community profile prestonModOp Level 2
Job title here
Location here
5 BADGES
Level 2

Level 2

Learn more
Joined the community 18-01-2018 3:21:19 PM
Offline
Top badges earned by prestonModOp
Customize the badges you want to showcase on your profile
Re: What’s the overhead of getting a resource resolver in...
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
Sorry for the duplicate.

Views

314

Likes

0

Replies

0
Re: What’s the overhead of getting a resource resolver in...
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
That's what we're doing. We're opening them for a specific bit of work and then closing them when done. The use case here is that we have this tag library that interrogates links and determines if they're a web page in the system. If they are it formats them a specific way. What this means, though, is that when you build the header in the site you effectively call this method hundreds of times. That's why I was wondering about the overhead of opening all of these ResourceResolver objects over an...

Views

315

Likes

0

Replies

0
Re: What’s the overhead of getting a resource resolver in...
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
That's what we're doing. We're opening them for a specific bit of work and then closing them when done.

Views

318

Likes

0

Replies

0
Re: What’s the overhead of getting a resource resolver in...
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
We're closing them. And we're using the getResourceResolver() method to retrieve them.

Views

291

Likes

0

Replies

0
Re: What’s the overhead of getting a resource resolver in...
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
We're closing resources correctly. What jumped out at me when I looked at our codebase in JProfiler was how long it took to even open a resourceResolver, regardless of the fact that we're closing it correctly. And we open hundreds of them per request. That's why I was curious about the overhead of even opening one.

Views

324

Likes

0

Replies

0
What’s the overhead of getting a resource resolver instance?
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
I inherited code for an application that uses resourceResolver instances quite liberally. Notably this code has a custom tag library for generating anchor tags. When called it takes the link and checks to see if it’s a page in the AEM using a resourceResolver. In the case of the navigation or footer it does this hundreds of times in total, per server hit. We’re struggling with performance issues and I set JProfiler against the application and that’s the only thing that jumps out. Moderately high...

Views

538

Likes

0

Replies

12
Re: Core AEM bundles restart when custom bundle is deployed
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
Anything else to help troubleshoot this? I did everything you said (which I believe comes from the article I originally cited). Here's what I see for Brightcove Connector. Importing Bundlescom.ourcompany (591)That's the end of the line on this scenario, right? And yet as a test I removed Brightcove Connector from our codebase and the core services no longer restart if I do that. What else can I do. One custom bundle imports another custom bundle. Neither exports each other or a core service.

Views

6.5K

Likes

0

Replies

1
Re: Core AEM bundles restart when custom bundle is deployed
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
Right. And this isn't what's happening with our setup. The only bundle importing either of the custom bundles is that one of them imports the other. No out of the box bundles import either custom bundle.

Views

6.5K

Likes

0

Replies

0
Re: Core AEM bundles restart when custom bundle is deployed
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
Nothing has worked so far. We're still stuck here.     

Views

6.5K

Likes

0

Replies

0
Re: Core AEM bundles restart when custom bundle is deployed
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
Jörg,Is that something you're getting from the MANIFEST file? That we're embedding core components? The bundle-plugin configuration for our project looks like this. ---- org.apache.felix maven-bundle-plugin true com.visitflorida.vf-harmony com.visitflorida.harmony.*, com.visitflorida.importer.*, com.visitflorida.searchpromote.*, com.visitflorida.form.* *;resolution:=optional com.visitflorida.harmony.models.components, com.visitflorida.harmony.models.templates, com.visitflorida.harmony.m-->-->${bundle.dynamicImport.package}-->...

Views

5.6K

Likes

0

Replies

1
Re: Core AEM bundles restart when custom bundle is deployed
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
We do not have bnd-maven-plugin in our pom.xml.

Views

5.6K

Likes

0

Replies

1
Re: Core AEM bundles restart when custom bundle is deployed
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
Here's the MANIFEST.MF from the bundle. Not sure what you mean by logs. Manifest-Version: 1.0Bnd-LastModified: 1555356723270Build-Jdk: 1.8.0_201Built-By: preston.workBundle-ClassPath: .,signpost-core-1.2.jar,signpost-commonshttp4-1.2.jar, core.wcm.components.core-1.1.0.jarBundle-Description: Maven Multimodule project for OurCompany.Bundle-ManifestVersion: 2Bundle-Name: OurCompany BundleBundle-SymbolicName: com.ourcompany.vf-harmonyBundle-Version: 0.0.1.SNAPSHOTCreated-By: Apache Maven Bundle Plu...

Views

5.6K

Likes

0

Replies

6
Re: Core AEM bundles restart when custom bundle is deployed
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
I did go through the steps to resolve it in that document. Neither of the custom bundles we deploy exports core libraries. This is what bundle-plugin configuration looks like. org.apache.felix maven-bundle-plugin true com.ourdomain.od-ourproject com.ourdomain.ourproject.*, com.ourdomain.importer.*, com.ourdomain.searchpromote.*, com.ourdomain.form.*, com.ourdomain.mediasite.* *;resolution:=optional com.ourdomain.ourproject.models.components, com.ourdomain.ourproject.models.templates, com...

Views

5.6K

Likes

0

Replies

8
Core AEM bundles restart when custom bundle is deployed
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
We're having trouble where our project, during deployment, causes a restart of all the core AEM bundles on every deploy. We're not certain when this bug was introduced or how to solve it. There appears to be some documentation of an error like this, but I don't feel we meet this criteria - Custom bundle install causes core AEM bundles to restart None of our custom bundles are exporting core libraries. Is there another potential cause? Or something similar to the above?

Views

6.8K

Like

1

Replies

18
Re: Following AEM 6.3 upgrade custom component configuration labels are missing
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
I played around with the POM settings and figured out the problem. I was using version 1.26.0 of the Felix maven-scr-plugin dependency. Once I switched back to 1.20.0 this stared working correctly. So that plugin should look like this. org.apache.felixmaven-scr-plugintruegenerate-scr-descriptorscr1.20.0

Views

991

Likes

0

Replies

0
Re: Following AEM 6.3 upgrade custom component configuration labels are missing
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
Try this use case meaning try a pom file like the above, but with a clean install and a basic component configuration?

Views

1.0K

Likes

0

Replies

0
Re: Following AEM 6.3 upgrade custom component configuration labels are missing
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
Why would labels and descriptions start working with AEM 6.3, though? Is there something we can do until we upgrade?

Views

997

Likes

0

Replies

0
Following AEM 6.3 upgrade custom component configuration labels are missing
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
We performed a 6.3 upgrade recently. For various reasons we stuck with Felix 1.9.8 annotations for now so I'm wondering if that's related. Anyway, labels and descriptions for our custom component configurations are missing. They look like this in the system config console. The code for our main pom.xml looks like it does below. I'm wondering if something in our Maven configuration is incorrect or if this is just how Felix-annotated configuration will look and we need to speed up the move to OSGI...

Views

2.1K

Likes

0

Replies

5
Re: Setting default folder properties in the DAM?
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
This is what we're trying to do. I don't believe in practice it works this way, though. It's looking like we have to manually set the smart tag setting on each sub folder.

Views

3.5K

Likes

0

Replies

0
Re: AEM 6.3 Event problem
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
Right. It's unfortunate in terms of documentation, though. I need to figure out how to call out documentation mistakes, because I think it is a mistake to have something marked as deprecated and not call out when the underlying functionality was removed. In terms of the solution, I've been working to implement a JCR EventListener. The main problem I can see is a potential performance problem as you essentially have to listen for every change or update event on a given path in the entire datastor...

Views

1.5K

Likes

0

Replies

0
Re: AEM 6.3 Event problem
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
I think this is what's throwing me off. When I think of deprecated I think of things that will be removed in the future. Not things that are being removed immediately. This feels like a documentation error on Adobe's part if I'm being honest. When I did the upgrade from 6.1 to 6.3 I explicitly looked for things that were being removed and dealt with those first. This wasn't noted as something that was being removed.

Views

1.5K

Likes

0

Replies

2
Re: Are event properties like resourceAddedAttributes and resourceChangedAttributes no longer supported in AEM 6.3?
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
I think you're right in hindsight. Fixing this.

Views

970

Likes

0

Replies

0
Re: DAM Smart Tags Assets workflow missing
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
For anyone who comes across this later, this happened because we did an in-place upgrade. We simply moved the workflow from a clean 6.3 server and everything works now. We also, incidentally, had to modify our custom schema to include the Smart Tags field because our custom schema didn't include it. More things to worry about for people who heavily customize AEM.

Views

873

Likes

0

Replies

0
Setting default folder properties in the DAM?
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
I need to configure our DAM such that from a certain folder down (all the children, children's children, children's children's children, etc.) are configured to with Smart Tagging enabled. Is there a way to do this in configuration or programmatically that I'm missing? It doesn't appear that properties cascade to children and I can't find a way to configure this to be possible.

Views

3.7K

Likes

0

Replies

3
Re: DAM Smart Tags Assets workflow missing
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
We're on 6.3.1.2.

Views

860

Likes

0

Replies

0
Re: DAM Smart Tags Assets workflow missing
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
I don't even see that workflow. What did we do wrong? That's my question.

Views

865

Likes

0

Replies

0
DAM Smart Tags Assets workflow missing
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
The documentation here - Smart Tags - indicates that it should be possible once Smart Tags are configured to start a workflow named "DAM Smart Tags Assets". I don't see that as an available workflow, though. What did I do wrong? I followed this documentation. Configuring Smart Tags Cloud Service

Views

2.2K

Likes

0

Replies

7
Re: AEM 6.3 Event problem
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
arunp99088702​ - I just tried a sample of an EventListener and it worked. I was able to see which property changed. In their sample code ACS Commons warns against using this often, it seems, saying...This is why I've been trying to get the ResourceChangeListener to work. Plus it seems more precise.

Views

4.5K

Likes

0

Replies

0
Re: AEM 6.3 Event problem
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
So like I said in my own thread I opened​, I'm having trouble with the ResourceChangeListener. I haven't tried an EventListener yet. I'm worried that I'll go to the trouble of implementing it and land in the same place.

Views

4.5K

Likes

0

Replies

1
Re: AEM 6.3 Event problem
Avatar
Validate 1
Level 2
prestonModOp
Level 2

Likes

3 likes

Total Posts

59 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
prestonModOp
- Adobe Experience Manager
You're using the EventListener, it looks like. Like the user above I tried a ResourceListener like this. I tried this code from Stack Overflow as a sanity check. When I debug this the addedPropertyNames and changedPropertyNames properties of "change" are null. I would expect to see what changed here.

Views

4.5K

Likes

0

Replies

0
Likes given to