reload on startup doesn't work in some cases

81 views
Skip to first unread message

ricardo...@incentro.com

unread,
May 28, 2015, 8:58:21 AM5/28/15
to hippo-c...@googlegroups.com
Hello,

I have a project running on hippo 7.8.9. There seems to occur some problems when I bootstrap content and run it on an "not-updated" storage.

For most content it works like expected. But I found 2 cases where I get this error.

[INFO] [talledLocalContainer] javax.jcr.nodetype.ConstraintViolationException: /content/documents/myproject/components/folder/folder/document/document: mandatory property {http://www.onehippo.org/jcr/hippo/nt/2.0.4}paths does not exist

In this case I'm trying to reload content/documents/myproject/components.xml

In /hippo:configuration/hippo:initialize/myproject-components the status is "pending"

When I look at the node where the violation occurs I see the paths property is missing. But I think this is something hippo should generate on its own for documents with mixin "harddocuments".


When I do a clean run, without storage, there are no problems. Everything loads correctly. I see that the paths property is set correctly. But in the console, I get the same error when I try to export the components node, delete the components node, reimport it and write changes to repository.

Does anybody understand what's causing this?

Bert Leunis

unread,
May 29, 2015, 4:06:43 AM5/29/15
to hippo-c...@googlegroups.com
Hi Ricardo,

On Thu, May 28, 2015 at 2:58 PM, <ricardo...@incentro.com> wrote:
Hello,

I have a project running on hippo 7.8.9. There seems to occur some problems when I bootstrap content and run it on an "not-updated" storage.

For most content it works like expected. But I found 2 cases where I get this error.

[INFO] [talledLocalContainer] javax.jcr.nodetype.ConstraintViolationException: /content/documents/myproject/components/folder/folder/document/document: mandatory property {http://www.onehippo.org/jcr/hippo/nt/2.0.4}paths does not exist

In this case I'm trying to reload content/documents/myproject/components.xml

In /hippo:configuration/hippo:initialize/myproject-components the status is "pending"

When I look at the node where the violation occurs I see the paths property is missing. But I think this is something hippo should generate on its own for documents with mixin "harddocuments".
This is indeed weird. The hippo:paths property is calculated using derived data. You can try: remove the property from a node and save it: it will appear again.
So it looks like the derived data function is not working in your case.
Is there a way you can share the faulty xml document with us? If you are working on a project for which a HES exist, you can file an issue for that project.


When I do a clean run, without storage, there are no problems. Everything loads correctly. I see that the paths property is set correctly. But in the console, I get the same error when I try to export the components node, delete the components node, reimport it and write changes to repository.

Does anybody understand what's causing this?

--
Hippo Community Group: The place for all discussions and announcements about Hippo CMS (and HST, repository etc. etc.)
 
To post to this group, send email to hippo-c...@googlegroups.com
RSS: https://groups.google.com/group/hippo-community/feed/rss_v2_0_msgs.xml?num=50
---
You received this message because you are subscribed to the Google Groups "Hippo Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hippo-communi...@googlegroups.com.
Visit this group at http://groups.google.com/group/hippo-community.
For more options, visit https://groups.google.com/d/optout.

ricardo...@incentro.com

unread,
May 29, 2015, 7:05:26 AM5/29/15
to hippo-c...@googlegroups.com
The problem has been found! It was a derative that wasn't being processed correctly.



Op vrijdag 29 mei 2015 10:06:43 UTC+2 schreef b.leunis:

Bert Leunis

unread,
Jun 1, 2015, 3:33:34 AM6/1/15
to hippo-c...@googlegroups.com
On Fri, May 29, 2015 at 1:05 PM, <ricardo...@incentro.com> wrote:
The problem has been found! It was a derative that wasn't being processed correctly.
Thanks for the feedback! So some derived data function went wrong, which caused a standard Hippo derived data function (for the hippo:paths property) to also fail? Interesting case.
 

Rick Beemsterboer

unread,
Jun 1, 2015, 3:44:22 AM6/1/15
to hippo-c...@googlegroups.com
That's exactly what happened. One of the derived data functions tried to use a non-existing field, resulting in an error, which apparently prevented other derived data functions (including the one that calculates the paths) from firing.

Rick
Rick Beemsterboer
Sr. Java Developer
HintTech Mastering the value of content
Mastering the value of content
creative | technology | content
Delftechpark 37i
2628 XJ Delft
The Netherlands
T:+31 88 268 25 00
M:+31 6 502 781 27
WebsiteTwitterFacebookLinkedIn
 

Bert Leunis

unread,
Jun 1, 2015, 3:50:21 AM6/1/15
to hippo-c...@googlegroups.com
On Mon, Jun 1, 2015 at 9:44 AM, Rick Beemsterboer <rick.bee...@hinttech.com> wrote:
That's exactly what happened. One of the derived data functions tried to use a non-existing field, resulting in an error, which apparently prevented other derived data functions (including the one that calculates the paths) from firing.
Good to know that that can happen. Nice find on your side!
 
Reply all
Reply to author
Forward
0 new messages