[MGNLDATA-256] EditDataActionDefinition does not support datatypes with namespace Created: 13/Jun/14  Updated: 17/Jul/14  Resolved: 11/Jul/14

Status: Closed
Project: Magnolia Data Module (closed)
Component/s: None
Affects Version/s: 2.2.2, 2.3
Fix Version/s: 2.2.3, 2.3.1

Type: Bug Priority: Major
Reporter: Erich Ruf Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLUI-2650 Nodes with colons not visible in JCR ... Closed
relates to MGNLDATA-260 ShowDataVersionActionDefinition does ... Closed
causality
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

We migrated our old custom data types to separate workspaces and created apps for each one as recommended. We also migrated our datatypes and added the namespace prefix 'mgnl:' (e.g. rating -> mgnl:rating) to each of them

In one case we have a tree view with two different data types. Therefore we used the EditDataActionDefinition from the data module to handle the default action properly. The "subAppMapping", which maps each datatype to the correct sub app, requires as jcr name the data type and as value the sub app.

Problem:
jcr names can't contain ':' which is used as separator for namespace and datatype name.

My workarround:
To solve this issue i encoded the jcr name (e.g. mgnl%3Arating) and added a decoding in the method 'setSubAppMapping' of my extended EditDataActionDefinition class.



 Comments   
Comment by Roman Kovařík [ 20/Jun/14 ]

Hello Erich,

a property name can actually contain a namespace. The problem is that tree view filters out these kind of properties, see MGNLUI-2650.
You can export subAppMapping node to check that properties are there although are not visible.

Hope that helps.
Roman

Comment by Erich Ruf [ 20/Jun/14 ]

Hi Roman,

The display issue in the JCR Browser is only one aspect of the problem. But i talk also about Node2BeanProcessing which is not working for property keys containing a colon character.
So this issue is related to MGNLUI-2650 but not a duplicate!

Please reopen the issue and provide a working solution.

Many thanks.
Erich

Comment by Roman Kovařík [ 23/Jun/14 ]

Hi Erich,

I see. I this case I would suggest to change the structure to something like:

  • subAppMapping
    • company
      • nodeType=company
      • subAppId=company

Thanks for pointing that out.

Regards.
Roman

Comment by Roman Kovařík [ 11/Jul/14 ]

Reopen: Updated bootstrap file is missing.

Generated at Mon Feb 12 05:12:52 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.