Hi,
I'm running into what seems to be an unsupported (but somewhat standard) usecase - I have a simple, 1:M relation:
@NodeEntity
public class Image {
@Fetch
@RelatedTo(type = "attr")
private Set<Attribute> attributes;
}
and
@NodeEntity
public class Attribute { ... }
The usecase is simply to change an Attribute on the Image and the persist (update) the Image and have the Attribute change as well - essentially cascading the persist operation on the association.
However, it seems that the RelatedToCollectionFieldAccessor will eventually call into: RelationshipHelper which does getOrCreateState. This method will just return the node if one exists (and create one if it doesn't) but will not allow it to update in any way.
So, my question is - is this usecase supported some other way, or does it have do be done manually for now; if not, should I open a JIRA / is there any plan to implement this kind of cascading functionality?
Any help is appreciated.
Thanks.
Eugen.