Q1: I'm trying to install a "redirect" page component package from AEM 5.6.1 to AEM 6.3 through package manager. Getting an error
"javax.jcr.nodetype.ConstraintViolationException: OakConstraint0021: /apps/******/components/page/redirect/dialog/items/tabs/items/leftNav/items/leftNavURL/items/link/component-a/component-a.jsp/jcr:content[[nt:resource]]: Mandatory property jcr:data not found in a new node"
Q2: Another non-container component named "component-a" is linked under dialog item "leftNavUrl".under redirect page component. Is it possible to do so in 6.3.
link under leftNavURL which is causing the exception.
<link
jcr:primaryType="cq:Widget"
fieldDescription="Select file from the Content Finder or enter complete URL."
itemId="webURL"
name="./directLink"
xtype="pathfield">
<template-a
cq:isContainer="{Boolean}false"
jcr:description="Component A"
jcr:primaryType="cq:Component"
jcr:title="Component A"
sling:resourceSuperType="foundation/components/page">
<dialog
jcr:primaryType="cq:Dialog"
height="400"
stateful="false"
xtype="dialog">
<items jcr:primaryType="cq:WidgetCollection">
<tabs jcr:primaryType="cq:TabPanel">
<items jcr:primaryType="cq:WidgetCollection">
Solved! Go to Solution.
I removed the error causing node and installed the package and it is installed now properly. I am investigating on what would be the expected node structure for that the one which is causing issue .
CT1012 Can you please paste a screenshot of the node structure for template-a.jsp here ?
Deploying a component in 5.6 to 6.3 may not work due to the changes in the JCR.
Can you please make a small package that contains this dialog. You component logic does not need to be there - put placeholder code. Then put the package on Google drive so community can attempt to deploy to AEM 6.3 and see if fixes can be made.
Views
Replies
Total Likes
Yes , Please share a sample code as scott explained. May be we can figure out the fix .
Views
Replies
Total Likes
Please access the following link Sample-component.zip - Google Drive
Views
Replies
Total Likes
I am looking into it now ..
Views
Replies
Total Likes
I am seeing the error too - looking deeper into this,
Views
Replies
Total Likes
I removed the error causing node and installed the package and it is installed now properly. I am investigating on what would be the expected node structure for that the one which is causing issue .
CT1012 Can you please paste a screenshot of the node structure for template-a.jsp here ?
AN FYI--- it works on 6.1 not 6.2 or 6.3. Remove the node as suggested by Veena.
You can use a tool like WinRaw:
Do you think the node structure you packaged and installing is correct ? do you think someone might have accidentally dragged and dropped a component inside your dialog node. Because what I see here in your node structure doesn't make sense to me
Because what I see here just makes me believe this was a total mistake in your node structure
Since it is a part of upgrade, no other developer is familiar with reasons and structures developed in 5.6.1. Initially i thought it was a mistake and installed it in AEM 6.3 without that error causing node.
For my future development concern just want to clear the air around this error, posted the same here to know the reason if anyone can clear the exception(unknown to me).
Appreciate your efforts veena and macdonald. Thank you
Views
Replies
Total Likes
I believe the same. Will keep you posted if i find any authoring errors after installing the modified component.
Views
Replies
Total Likes
@CT1012 the template-a and its node sturcture clearly says its a mistake .. hope you can figure out if something is wrong
thanks
Veena
Views
Replies
Total Likes