Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

radhakrishnan72
radhakrishnan72
Offline

Badges

Badges
11

Accepted Solutions

Accepted Solutions
0

Likes Received

Likes Received
4

Posts

Posts
28

Discussions

Discussions
19

Questions

Questions
9

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by radhakrishnan72
Customize the badges you want to showcase on your profile
Re: java.lang.IllegalArgumentException: Value for key (property name) can't be put into node - Adobe Experience Manager 29-01-2018
Hi smacdonald2008, thanks for your quick update. Usage of API is ok. Is there any chance of write up on difference between Asset Manager API and using resolver and then modifiable map for updates? It would be great help here for understanding more.Thanks & Regards,Radhakrishna.

Views

6.1K

Likes

0

Replies

3
Re: java.lang.IllegalArgumentException: Value for key (property name) can't be put into node - Adobe Experience Manager 29-01-2018
Hi smacdonald2008, Could you please let me know, if there is any update about this?Thanks & Regards,Radhakrishna.

Views

6.1K

Likes

0

Replies

5
Re: javax.jcr.InvalidItemStateException: OakState0001: Unresolved conflicts in asset when publishing - Adobe Experience Manager 29-01-2018
Hi kautuksahni, i have some of the doubts. Could you please clarify them so that i can best use them?I use to get session from adapting it from resource resolver. Is it really required to immediately close current session after piece of work?I am aware resolver closes it when resolver is closed.Is it recommended to open and close multiple sessions to process (seq of operations) one asset?Is it recommended to call refresh on session every time as application process thousands of assets in a day?I...

Views

4.2K

Likes

0

Replies

1
Re: javax.jcr.InvalidItemStateException: OakState0001: Unresolved conflicts in asset when publishing - Adobe Experience Manager 29-01-2018
Hi smacdonald2008, the processing and replication process is a custom process. Processing metadata takes first in the sequence and replication using replication API. Any asset has to go through these two steps. I have to set up "JCR write logging" to look into more details. I am waiting to get more load on the instance.Thanks & Regards,Radhakrishna.

Views

4.2K

Likes

0

Replies

0
Re: javax.jcr.InvalidItemStateException: OakState0001: Unresolved conflicts in asset when publishing - Adobe Experience Manager 29-01-2018
Hi Jörg Hoh, thanks for asking this question. I have seen these two exceptions in different times based on understanding i have for last few months.Thanks & Regards,Radhakrishna.

Views

4.2K

Likes

0

Replies

2
Re: java.lang.IllegalArgumentException: Value for key (property name) can't be put into node - Adobe Experience Manager 26-01-2018
Hi smacdonald2008, thanks for making a point to use specific API when using corresponding functionality. I do follow Yadav Brijesh and your recommendations here on. It would be great information for everyone, if we have exact difference between them.I am very much interested to know about this exception.Thanks & Regards,Radhakrishna.

Views

10.7K

Likes

0

Replies

7
Re: java.lang.IllegalArgumentException: Value for key (property name) can't be put into node - Adobe Experience Manager 26-01-2018
Hi Yadav Brijesh, thanks for your suggestion. I would look to understand your suggestion using Asset API. What advantage are we going to get when compared to Resource. Can you please help putting your view here and how that helps this problem to be solved?Thanks & Regards,Radhakrishna.

Views

10.7K

Likes

0

Replies

9
Re: java.lang.IllegalArgumentException: Value for key (property name) can't be put into node - Adobe Experience Manager 26-01-2018
Hi rmahendr the values(create/update/delete) i use are of string type. The second property takes string[] type values.Thanks & Regards,Radhakrishna.

Views

10.7K

Likes

0

Replies

0
Re: oakState0002: Conflicting concurrent change on branch commits - Adobe Experience Manager 26-01-2018
Hi Jörg Hoh​, thanks for your quick reply here. I set up this log, analyze and update here.Thanks & Regards,Radhakrishna.

Views

1.3K

Likes

0

Replies

0
Re: java.lang.IllegalArgumentException: Value for key (property name) can't be put into node - Adobe Experience Manager 25-01-2018
Thanks for letting me know, smacdonald2008Here is the code snippet for the same,String customValue = "update";Resource assetRsc = resolver.getResource("path/to/asset/metadata");if(assetRsc !=null) { ModifiableValueMap properties = assetRsc.adaptTo(ModifiableValueMap.class); properties.put("custom_property", customValue ); // some more properties to be set here saveToRepo(resolver);}private void saveToRepo(ResourceResolver resolver){try {resolver.commit();} catch (PersistenceException e) {logger....

Views

10.7K

Likes

0

Replies

2