[
http://issues.ops4j.org/browse/QI-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709#action_12709
]
Niclas Hedhman commented on QI-217:
-----------------------------------
This is actually much harder than it sounds. Properties of ValueComposite are
collapsed in DefaultEntityState into a single string, and it seems impossible
to dig out the type information.
One could possible convert a ValueComposite property from;
<value
xmlns="urn:qi4j:type:org.qi4j.library.rdf.entity.TestEntity#">{test1:5,test2:null,test3:{data:"Habba"}}</value>
to
<value xmlns="urn:qi4j:type:org.qi4j.library.rdf.entity.TestEntity#">
<test1>5</test1>
<test2>null</test2>
<test3>
<data>Habba</data>
</test>
</value>
The xmlns setting should make the nodes belong to the right namespace.
> ValueComposite should be indexed as a node structure
> ----------------------------------------------------
>
> Key: QI-217
> URL: http://issues.ops4j.org/browse/QI-217
> Project: Qi4j
> Issue Type: Improvement
> Components: Indexing
> Reporter: Niclas Hedhman
> Assignee: Niclas Hedhman
> Fix For: 1.0
>
>
> ValueComposites are currently 'serialized' into a single RDF node. This
> prohibits querying for partial values somewhere among the values. The
> ValueComposite should become a node pointing to nodes of its properties.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
