[JBoss JIRA] (TEIIDDES-1996) Add Problems tab in VDB editor to view warnings and errors if present in VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1996?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1996.
------------------------------------
Resolution: Done
Model Problems tab is now available in the VDB Editor.
Note also fixed some refresh issues with VDB Editor's selectted model-related info panels.
> Add Problems tab in VDB editor to view warnings and errors if present in VDB
> ----------------------------------------------------------------------------
>
> Key: TEIIDDES-1996
> URL: https://issues.jboss.org/browse/TEIIDDES-1996
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Editors, VDB & Execution
> Affects Versions: 8.3
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 8.3.x
>
> Attachments: vdb-editor-problems-tab.png
>
>
> If a VDB has errors and can't be deployed, there's no way to view those error messages in the VDB editor.
> Add a Problems tab next to the Source Binding Definition tab and display problems in table for selected model.
--
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
12 years, 4 months
[JBoss JIRA] (TEIIDDES-1861) Designer deletes data role "condition" information
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1861?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1861.
------------------------------------
Resolution: Out of Date
Marking this as Out Of Date.
Re-importing the project set will result in validation errors which will need to be fixed by wrapping table names in double-quotes. Setting a condition on these tables will work properly.
Re-importing source models will result in table names properly wrapped in double-quotes and get to the same state.
See TEIIDDES-1993 for details on the fix and changed import and validation behavior
> Designer deletes data role "condition" information
> --------------------------------------------------
>
> Key: TEIIDDES-1861
> URL: https://issues.jboss.org/browse/TEIIDDES-1861
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration, VDB & Execution
> Affects Versions: 8.2
> Environment: Windows 7, Eclipse kepler.
> Reporter: Pablo Navascues
> Assignee: Barry LaFond
> Fix For: 8.3.x
>
> Attachments: Teiiddes-1861-screencapture.m4v
>
>
> Create a VDB
> Create a source model by importing from JDBC
> Add model to VDB
> Define data role with a table wide condition like "USERNAME=substring(user(), 1, locate('@', user()) - 1)"
> Synchronize, save VBD.
> Condition is applied to queries, can be seen in the designer, can be seen in the VBD internal xml.
> Keep working and after another save (not necessarily de second one) condition field value is empty in designer and gone from teh XML as well.
> This has happened more than once and to more than one developer in the team.
--
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
12 years, 4 months
[JBoss JIRA] (TEIIDDES-1998) Connection Profile loses Binding Type
by Ted Jones (JIRA)
Ted Jones created TEIIDDES-1998:
-----------------------------------
Summary: Connection Profile loses Binding Type
Key: TEIIDDES-1998
URL: https://issues.jboss.org/browse/TEIIDDES-1998
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 8.3
Reporter: Ted Jones
Assignee: Barry LaFond
Whenever importing WSDL into Source model, the connection profile loses it's binding info and I am required to edit the CP and add the binding info with each import. We should find a way to persist it or some other way to get the binding for import.
The error is: "Connection Profile is invalid since it does not contain the required property DefaultBinding".
--
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
12 years, 4 months
[JBoss JIRA] (TEIIDDES-1997) Deleting virtual table, break column mappings for unrelated virtual table
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1997?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1997:
----------------------------------------
Seems like the ObjectDeleteCommand was merged with ResourceRefactorCommand and ended up with some "unload" calls to the related resources.
This resulted in source table EObjects being proxies and could not be resolved, hence they were orphaned by EMF.
Fix is to remove the unload logic from ObjectDeleteCommand.
> Deleting virtual table, break column mappings for unrelated virtual table
> -------------------------------------------------------------------------
>
> Key: TEIIDDES-1997
> URL: https://issues.jboss.org/browse/TEIIDDES-1997
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.3
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 8.3.x
>
>
> 1) Source and View models
> 2) View model contains virtual table selecting from source table
> 3) View model contains second virtual table (empty)
> 4) Select and Delete empty virtual table
> 5) Column mapping hrefs are broken for the first virtual table
--
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
12 years, 4 months
[JBoss JIRA] (TEIIDDES-1997) Deleting virtual table, break column mappings for unrelated virtual table
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-1997:
--------------------------------------
Summary: Deleting virtual table, break column mappings for unrelated virtual table
Key: TEIIDDES-1997
URL: https://issues.jboss.org/browse/TEIIDDES-1997
Project: Teiid Designer
Issue Type: Bug
Components: Modeling
Affects Versions: 8.3
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 8.3.x
1) Source and View models
2) View model contains virtual table selecting from source table
3) View model contains second virtual table (empty)
4) Select and Delete empty virtual table
5) Column mapping hrefs are broken for the first virtual table
--
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
12 years, 4 months
[JBoss JIRA] (TEIIDDES-1996) Add Problems tab in VDB editor to view warnings and errors if present in VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1996?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1996:
----------------------------------------
The attached image captures the new Problems Tab in the VDB Editor along with the Problems view displaying same markers.
Note the Model Explorer VDB is decorated with an ERROR to further reflect the state of the VDB outside the editor.
> Add Problems tab in VDB editor to view warnings and errors if present in VDB
> ----------------------------------------------------------------------------
>
> Key: TEIIDDES-1996
> URL: https://issues.jboss.org/browse/TEIIDDES-1996
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Editors, VDB & Execution
> Affects Versions: 8.3
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 8.3.x
>
> Attachments: vdb-editor-problems-tab.png
>
>
> If a VDB has errors and can't be deployed, there's no way to view those error messages in the VDB editor.
> Add a Problems tab next to the Source Binding Definition tab and display problems in table for selected model.
--
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
12 years, 4 months