Skip to content

Multiple instances are generated when using additional nodes within domain elements #84

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ymark opened this issue Mar 9, 2017 · 1 comment
Labels

Comments

@ymark
Copy link
Collaborator

ymark commented Mar 9, 2017

When an additional node is declared inside a domain node then multiple instances of the entity declared inside the additional node are generated. For example the following part of the x3ml mappings file

<domain>
   <source_node>//COIN</source_node>
   <target_node>
      <entity>
         <type>crm:E22_Man-Made_Object</type>
         <instance_generator name="UUID"/>
         <additional>
            <relationship>crm:PX1_is_made_of</relationship>
            <entity>
               <type>crm:EX1_Material</type>
                  <instance_generator name="UUID"/>
            </entity>
         </additional>
      </entity>
   </target_node>
</domain>

will create 2 instances of the crm:EX1_Material class: the first one properly connected with the corresponding crm:E22_Man-Made_Object and the other one will be orphan (It will not have any incoming properties).

@ymark
Copy link
Collaborator Author

ymark commented Mar 9, 2017

This issue has been raised because domain nodes where resolved twice.
Added an extra check so if a domain has already been resolved, it will not happen again.

The bug-free version of the X3ML Engine will be made available starting from version 1.7.5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant