[JBoss JIRA] (TEIIDDES-2157) Problem markers removed from models during clean build
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2157?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2157.
------------------------------------
Resolution: Done
Changed deleteMarkers() calls to use DEPTH_ZERO instead of DEPTH_INFINITE
> Problem markers removed from models during clean build
> ------------------------------------------------------
>
> Key: TEIIDDES-2157
> URL: https://issues.jboss.org/browse/TEIIDDES-2157
> Project: Teiid Designer
> Issue Type: Bug
> Components: Validation
> Affects Versions: 8.5
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 8.5
>
>
> 1) Import the attached project
> 2) Open source model package diagram and force validation by moving table in diagram and saving. This should create an error marker for the table.
> 3) Select *Project > Clean...* action to rebuild project
> 4) All problem markers are deleted
> *Note that Clean...for this project works fine in 8.3.2*
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2157) Problem markers removed from models during clean build
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2157?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2157:
--------------------------------------
Assignee: Barry LaFond (was: Paul Richardson)
> Problem markers removed from models during clean build
> ------------------------------------------------------
>
> Key: TEIIDDES-2157
> URL: https://issues.jboss.org/browse/TEIIDDES-2157
> Project: Teiid Designer
> Issue Type: Bug
> Components: Validation
> Affects Versions: 8.5
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 8.5
>
>
> 1) Import the attached project
> 2) Open source model package diagram and force validation by moving table in diagram and saving. This should create an error marker for the table.
> 3) Select *Project > Clean...* action to rebuild project
> 4) All problem markers are deleted
> *Note that Clean...for this project works fine in 8.3.2*
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2157) Problem markers removed from models during clean build
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-2157:
--------------------------------------
Summary: Problem markers removed from models during clean build
Key: TEIIDDES-2157
URL: https://issues.jboss.org/browse/TEIIDDES-2157
Project: Teiid Designer
Issue Type: Bug
Components: Validation
Affects Versions: 8.5
Reporter: Barry LaFond
Assignee: Paul Richardson
Priority: Blocker
Fix For: 8.5
1) Import the attached project
2) Open source model package diagram and force validation by moving table in diagram and saving. This should create an error marker for the table.
3) Select *Project > Clean...* action to rebuild project
4) All problem markers are deleted
*Note that Clean...for this project works fine in 8.3.2*
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2156) Building Vdbs in eclipse should not throw runtime exceptions
by Paul Richardson (JIRA)
Paul Richardson created TEIIDDES-2156:
-----------------------------------------
Summary: Building Vdbs in eclipse should not throw runtime exceptions
Key: TEIIDDES-2156
URL: https://issues.jboss.org/browse/TEIIDDES-2156
Project: Teiid Designer
Issue Type: Bug
Components: Eclipse Integration
Affects Versions: 8.3.2, 8.5
Reporter: Paul Richardson
Assignee: Paul Richardson
Fix For: 8.5, 8.3.3
When the VdbBuilder is initialised, it starts looking for all the vdb files in the workspace and synchronizes them and other housekeeping tasks. Such tasks involve the creation of a Designer Vdb pojo which uses the OperationUtil.perform(Unreliable) method.
This method will throw a runtime exception if an exception occurs within Unreliable's operations. However, should an exception be thrown, all building in Eclipse will cease as a runtime exception is not handled by the BuilderManager.
Runtime exceptions in this case should be replaced with normal exceptions which will be properly handled in code and allow other builder tasks to continue.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-305) Create an importer for the LDAP Connector
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-305?page=com.atlassian.jira.plug... ]
Paul Richardson resolved TEIIDDES-305.
--------------------------------------
Resolution: Done
commit f83605f2a6 backported to 8.3.x branch exposing ldap importer.
> Create an importer for the LDAP Connector
> -----------------------------------------
>
> Key: TEIIDDES-305
> URL: https://issues.jboss.org/browse/TEIIDDES-305
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Import/Export
> Affects Versions: Future
> Reporter: Michael Walker
> Assignee: Barry LaFond
> Fix For: 8.3.3, 8.3
>
>
> Designer should be able to import LDAP metadata and auto-generate a relational model. This would remove the manual effort of creating models, which is error-prone.
> The importer should support the ability to gather cost statistics, as it greatly enhances overall query performance, and is always recommended for use with LDAP data source connections.
> The importer could also create normalized tables to represent multi-valued attributes of a given DN. See linked issue for more info on this request.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months