[JBoss JIRA] (TEIIDDES-288) Navigation Problem In Search Result View When Multiple Resources Involved
by Dan Florian (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-288?page=com.atlassian.jira.plug... ]
Dan Florian updated TEIIDDES-288:
---------------------------------
Assignee: Barry LaFond (was: Dan Florian)
Not sure if these issues are still valid or not. Assigning to Barry to edit and reassign.
> Navigation Problem In Search Result View When Multiple Resources Involved
> -------------------------------------------------------------------------
>
> Key: TEIIDDES-288
> URL: https://issues.jboss.org/browse/TEIIDDES-288
> Project: Teiid Designer
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Dan Florian
> Assignee: Barry LaFond
>
> When using tree layout in the search results view, if matches are shown from multiple resources, the up/down toolbar navigation buttons will not navigate to the previous/next match if the match is in a different resource. This was not entirely implented. See MetadataSearchResultPage.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 2 months
[JBoss JIRA] (TEIIDDES-1128) Implement The Model Registry View's Find Reference Action
by Dan Florian (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1128?page=com.atlassian.jira.plu... ]
Dan Florian updated TEIIDDES-1128:
----------------------------------
Assignee: Barry LaFond (was: Dan Florian)
Not sure if these issues are still valid or not. Assigning to Barry to edit and reassign.
> Implement The Model Registry View's Find Reference Action
> ---------------------------------------------------------
>
> Key: TEIIDDES-1128
> URL: https://issues.jboss.org/browse/TEIIDDES-1128
> Project: Teiid Designer
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Views
> Affects Versions: 7.6
> Reporter: Dan Florian
> Assignee: Barry LaFond
> Fix For: Future
>
>
> The "Find References" action will find all models that have applied the selected model extension definition. The results of the action should be displayed in Eclipse's search results view. Double-click in the results should open the model. The design of the search results should patterned after the Java->References results.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 2 months
[JBoss JIRA] (TEIIDDES-1153) Create Model Extension Definition (MED) Compare Editor
by Dan Florian (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1153?page=com.atlassian.jira.plu... ]
Dan Florian updated TEIIDDES-1153:
----------------------------------
Assignee: Barry LaFond (was: Dan Florian)
Not sure if these issues are still valid or not. Assigning to Barry to edit and reassign.
> Create Model Extension Definition (MED) Compare Editor
> ------------------------------------------------------
>
> Key: TEIIDDES-1153
> URL: https://issues.jboss.org/browse/TEIIDDES-1153
> Project: Teiid Designer
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Editors
> Affects Versions: 7.6
> Reporter: Dan Florian
> Assignee: Barry LaFond
> Fix For: Future
>
> Attachments: ModelExtensionDefinitionCompareInput.java
>
>
> It is important for a user to know the differences between a MED in the registry and the same MED in the workspace. The MED in the workspace may have changes and the user should be able to see those differences. The compare editor should also be able to compare MEDs that are both in the workspace. When comparing with a registry MED, the registry MED is readonly and cannot be changed by the compare editor. Eclipse has a compare editor framework that should be used. One approach would be to use the built-in text compare editor but having a GUI compare editor might be nicer.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 2 months
[JBoss JIRA] (TEIIDDES-1129) Create IContentOutlinePage Implementation For Model Extension Definition Editor
by Dan Florian (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1129?page=com.atlassian.jira.plu... ]
Dan Florian updated TEIIDDES-1129:
----------------------------------
Assignee: Barry LaFond (was: Dan Florian)
Not sure if these issues are still valid or not. Assigning to Barry to edit and reassign.
> Create IContentOutlinePage Implementation For Model Extension Definition Editor
> -------------------------------------------------------------------------------
>
> Key: TEIIDDES-1129
> URL: https://issues.jboss.org/browse/TEIIDDES-1129
> Project: Teiid Designer
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Editors, Views
> Affects Versions: 7.6
> Reporter: Dan Florian
> Assignee: Barry LaFond
> Fix For: Future
>
>
> The outline page view should correspond to the model extension definition (MED) structure and be patterned after Eclipse's Java editor. Selection should be sync'd between the MED editor and the outline view. Actions in the outline should correspond to the appropriate actions in the editor. For instance, if selecting a metaclass in the outline view, two actions could be "Add Extension Property" and "Remove Metaclass."
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 2 months
[JBoss JIRA] (TEIIDDES-714) Designer should clean up preview vdbs every time Teiid Server connection is made.
by Dan Florian (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-714?page=com.atlassian.jira.plug... ]
Dan Florian updated TEIIDDES-714:
---------------------------------
Assignee: Barry LaFond (was: Dan Florian)
Not sure if these issues are still valid or not. Assigning to Barry to edit and reassign.
> Designer should clean up preview vdbs every time Teiid Server connection is made.
> ---------------------------------------------------------------------------------
>
> Key: TEIIDDES-714
> URL: https://issues.jboss.org/browse/TEIIDDES-714
> Project: Teiid Designer
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Teiid Integration
> Affects Versions: 7.1
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Fix For: Future
>
>
> It is quite possible that that the preview vdbs deployed into a Teiid Server get out of sync with the Designer when the Server is restarted independent of the Designer. Since Designer keeps track of its preview vdbs based on workspace uuid, it is better that it cleans up its preview vdbs and data sources when the connection is made and connection is cleaned up. These actions may happen at both startup and shutdown of the Designer and also at the creation and discard of the Server settings once the Designer started. Otherwise there may be orphan VDBs left over in the Server.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 2 months
[JBoss JIRA] (TEIIDDES-696) Clicking "Restore Default" in Editor Prefs deletes entries from list of tables
by Dan Florian (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-696?page=com.atlassian.jira.plug... ]
Dan Florian updated TEIIDDES-696:
---------------------------------
Assignee: Barry LaFond (was: Dan Florian)
Not sure if these issues are still valid or not. Assigning to Barry to edit and reassign.
> Clicking "Restore Default" in Editor Prefs deletes entries from list of tables
> ------------------------------------------------------------------------------
>
> Key: TEIIDDES-696
> URL: https://issues.jboss.org/browse/TEIIDDES-696
> Project: Teiid Designer
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Dialogs
> Affects Versions: 7.1.1
> Environment: Windows, JBDS 4.0 Beta 1
> Reporter: Paul Nittel
> Assignee: Barry LaFond
> Priority: Minor
> Fix For: Future
>
> Attachments: EvenMoreMissing.jpg, TablesWithSomeMissing.jpg
>
>
> I was testing the Windows > Preferences > Teiid Designer > Editor - Table Tab and went to restore the default values, after reordering columns in the Columns table. When I did so, the entry for the Columns table vanished! Tried it again on a couple of other table entries and they, too, were removed from the list. I clicked OK. Looked again and they were gone. Restarted the Designer and they were still gone.
> Had I canceled, it would have been OK, but it shouldn't have happened anyway.
> Happy Halloween? (Screenshots are attached. No exceptions were noted.)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 2 months
[JBoss JIRA] (TEIIDDES-1144) Investigate If The Model Extension Definition Validation Done In The Editor Can Be Done Using XSD Validation
by Dan Florian (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1144?page=com.atlassian.jira.plu... ]
Dan Florian updated TEIIDDES-1144:
----------------------------------
Assignee: Barry LaFond (was: Dan Florian)
Not sure if these issues are still valid or not. Assigning to Barry to edit and reassign.
> Investigate If The Model Extension Definition Validation Done In The Editor Can Be Done Using XSD Validation
> ------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1144
> URL: https://issues.jboss.org/browse/TEIIDDES-1144
> Project: Teiid Designer
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Editors
> Affects Versions: 7.6
> Reporter: Dan Florian
> Assignee: Barry LaFond
> Fix For: Future
>
>
> The validation being done as the user is editing a MED is done using the ModelExtensionDefinitionValidator (MEDValidator). This validator tries to recreate in code what the MED XSD does when the MED file is parsed. The MEDValidator should use XSD validation libraries to perform validation to guarantee that MED problem markers agree with those reported in the editor.
> Looking into this a bit I found that XSD validation libraries only validate entire documents. So to validate just an element value or simple type value does not seem possible. One possible way around this might be to create XML fragments to match the smaller sections of that document that require validation. Research still needs to be done on the feasibility of this idea.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 2 months