[
https://issues.jboss.org/browse/TEIIDDES-1387?page=com.atlassian.jira.plu...
]
Ted Jones edited comment on TEIIDDES-1387 at 7/15/13 3:50 PM:
--------------------------------------------------------------
The ModelWorkspaceManager did not contain the newly created project when we tried to add
the model resource since this happens when a resource is added. Changed to use
ModelerCore.getWorkspace().getRoot().findMember(location) to get the project or project
folder. Also broke logic out into a separate method in ModelerCore since this was needed
in several classes for view and source models (XML, Flat File, Relational).
was (Author: tejones):
The ModelWorkspaceManager did not contain the newly created project when we tried to
add the model resource since this happens when a resource is added. Changed to use
ModelerCore.getWorkspace().getRoot().findMember(location) to get the project or project
folder. Also broke logic out into a separate method in ModelErCore since this was needed
in several classes for view and source models (XML, Flat File, Relational).
Encountered NPE during XML Remote import
----------------------------------------
Key: TEIIDDES-1387
URL:
https://issues.jboss.org/browse/TEIIDDES-1387
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 7.7.1
Reporter: Mark Drilling
Assignee: Ted Jones
Priority: Blocker
Fix For: 8.2
Attachments: PlantCatException.txt
Encountered NPE during import of the PlantCatalog remote XML file example -
http://www.w3schools.com/xml/plant_catalog.xml
I think the issue was - I added the Plant child Elements, but left the 'root
path' at the document root. However, when I re-tried the scenario - I didnt get the
NPE again. Anyway, I am attaching the stacktrace - we may be able to figure out the issue
from that.
This may be something we want to address for usability - maybe we can do some validation
to ensure that the root path is appropriate for the selected elements?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira