Expand my Community achievements bar.

SOLVED

AEM Page, why jcr:created timestamp is changing when new changes are published.

Avatar

Level 1

jcr:created time stamp is changing in publisher when new changes are published though in author it remain the same.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

I observed this behavior in old versions of AEM (6.2, 6.1) and also in AEM 6.4, whenever a page is activated jcr:created property will have the last activation date and it differs between author and publisher

You can check AEM performance issue with Java 7 -- Below is the content in the page

Question

Why jcr:created property is being changed in case of any activation?

Answer

This is a common misunderstanding that you are updating the same node on the publisher.
What is actually happening is that you are creating a new version of the node when you activate it and on the publisher, you then insert the new node instead of the old one. If you look at the jcr:content of your node in the Publisher, then you will notice the properties jcr:baseVersion, jcr:predecessors and jcr:versionHistory that are all of the type Reference (or Reference array). Take a look at them nodes and you will find the "old ones". There is a lot of things going on under the surface when creating the nodes. Same thing happens on the author side.

View solution in original post

4 Replies

Avatar

Community Advisor

I checked in AEM 6.3 and jcr:created is not changing in publish env.

I publish the we-retail.

Can you please post screenshots.

Avatar

Correct answer by
Community Advisor

I observed this behavior in old versions of AEM (6.2, 6.1) and also in AEM 6.4, whenever a page is activated jcr:created property will have the last activation date and it differs between author and publisher

You can check AEM performance issue with Java 7 -- Below is the content in the page

Question

Why jcr:created property is being changed in case of any activation?

Answer

This is a common misunderstanding that you are updating the same node on the publisher.
What is actually happening is that you are creating a new version of the node when you activate it and on the publisher, you then insert the new node instead of the old one. If you look at the jcr:content of your node in the Publisher, then you will notice the properties jcr:baseVersion, jcr:predecessors and jcr:versionHistory that are all of the type Reference (or Reference array). Take a look at them nodes and you will find the "old ones". There is a lot of things going on under the surface when creating the nodes. Same thing happens on the author side.

Avatar

Level 1

"There is a lot of things going on under the surface when creating the nodes. Same thing happens on the author side."
Would you please provide some documentation or any other resource from where I can learn what's happening in detail especially what's going on in the publish instance during page activation/replication. As a new community member, I am a little confused about finding the proper docs.

Avatar

Level 1

I tried the same in fresh aem 6.4.3 with author and publish and I can see this error. Created a video of that and posting that here via youtube. You can notice date is getting changed.