[ https://jira.jboss.org/jira/browse/TEIIDDES-132?page=com.atlassian.jira.p... ] John Doyle updated TEIIDDES-132: -------------------------------- Attachment: teiiddes_132.zip -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/TEIIDDES-132?page=com.atlassian.jira.p... ] John Doyle commented on TEIIDDES-132: ------------------------------------- This issue also happens in a VDB with the salesforce model extensions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/TEIIDDES-132?page=com.atlassian.jira.p... ] Barry LaFond commented on TEIIDDES-132: --------------------------------------- Problem is NOT the UUID, the problem is that EMF has changed with respect to the child behavior of the Extension model. 1) During validation, the ModelObjectCollector walks the eObjects using eObject.eContents() method. 2) in 5.5.3 XAttribute.eContents() returned EMPTY list. 3) In Teiid Designer, XAttribute.eContents() returns a List containing the EGenericTypeImpl, so we go ahead and run the EObjectUuidRule on it and of course it fails. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/TEIIDDES-132?page=com.atlassian.jira.p... ] Johnny Verhaeg resolved TEIIDDES-132. ------------------------------------- Resolution: Done The XMLSOAPConnectorExtensions model causing the validation errors is a metamodel extension model. The Designer has 2 facilities for assigning UUIDs to objects: 1) During the load process via the MtkXmiHandler, and 2) via and EContentAdapter as objects are created by the user and attached to a resource. Unlike previous versions, EMF is now dynamically adding content to extended attributes in metamodel extension models to identify an attributes data type, without involving the XMI handler. Not sure if this is an error on EMF's part, but to fix I had to add a content iterator after the load process that ensures all contents has a UUID. The loop is an admittedly inefficient way of handling this, but I don't currently have a viable alternative. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira