[JBoss JIRA] Created: (TEIIDDES-261) The Designer Eclipse Feature Should Be Separated Into A Design-Time Feature And A Runtime-Time Feature
10:26 a.m.
The Designer Eclipse Feature Should Be Separated Into A Design-Time Feature And A
Runtime-Time Feature
------------------------------------------------------------------------------------------------------
Key: TEIIDDES-261
URL: https://jira.jboss.org/jira/browse/TEIIDDES-261
Project: Teiid Designer
Issue Type: Task
Affects Versions: 7.0
Reporter: Dan Florian
Fix For: 7.0
A version of Teiid Designer should be available that does not include the ability to
perform data preview, connection management, and VDB execution. This design-time Designer
would be suited to users that are strictly data modelers. A "design-time only"
Designer would have a reduced footprint over the current Designer. Another Designer that
is more suited to users that test models and VDBs would then be needed. We would build
this Designer by adding on the data preview, connection management, and VDB execution
capabilities to the "design-time only" Designer. Eclipse features are the way
that different builds of the Designer can be accomplished.
We have done a pretty good job of isolating the data preview, connection management, and
VDB execution code into their own Eclipse plugins. The Eclipse plugins that were designed
to handle these capabilities are the dqp, dqp.ui, and sqlexplorer plugins. However, there
are a few cases of code found in "design-time only" plugins that depend on these
data preview, connection management, and VDB execution plugins. These cases will have to
be addressed in order to complete this task. Separate JIRAs should be written for these
cases as they are found and tied to this JIRA.
--
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
2:15 p.m.
New subject: [JBoss JIRA] Commented: (TEIIDDES-261) The Designer Eclipse Feature Should Be Separated Into A Design-Time Feature And A Runtime-Time Feature
[
https://jira.jboss.org/jira/browse/TEIIDDES-261?page=com.atlassian.jira.p...
]
Barry LaFond commented on TEIIDDES-261:
---------------------------------------
To better accommodate changes required for JBoss Tools integration and Teiid 7.0
integration we propose to modify/refactor our current code-base in the following way.
We propose to separate Teiid Designer code into Design-time code and Run-time code
resulting in two installable Eclipse-based feature sets.
* Design-time is specified as all modeling exercises short of
creating/editing/executing VDB's or previewing data.
o Users can create model projects, import/create/edit models, organize models
into projects and folders, check-in/check-out from their favorite repository, etc....
o UDF modeling will still be available.
o Importing data for model creation will NOT auto-create connectors and data
preview feature will not be available.
o The VDB will NOT be a visible concept.
* Run-time refers to any data preview or VDB execution logic
o This feature will initially depend on installed Design-time features to run.
o Users can create/edit/execute VBD's.
o Importing data for model creation will auto-create connectors.
o Data Preview will be available for design-time modeling.
o Auto-deploy VDB to Teiid server (stretch)
o Modify DQP/SQL Explorer plugins to execute VDB via DTP's jdbc connection
to Teiid.
o No Designer-related jar management for UDF of JDBC/JDBC connections (assumed
to be in place on server)
Motivating factors for making these changes to Designer include:
* Creation of lighter-weight tool which is NOT dependent on Teiid runtime code-base
will facilitate easier development of the modeling features.
* Eliminates duplicate code maintenance between Designer and Teiid.
* Allows independent run-time feature development.
* Simplifies run-time features by removing non-essential Eclipse dependencies (EMF,
UML2, etc...)
There will be a few milestones related to our 7.0 release
M1 - Design-time tooling feature set (modeling only)
* separation of any preview data or vdb execution from modeling
* keep current JDBC import methodology
M2 - Run-time execution tooling feature set (add-on to design-time feature set)
* utilizes current SQL Explorer
M3 - Integration of Designer with DTP functionality
* remove SQL Explorer and replace with common DTP data source querying
* customize through DTP to perform preview data queries.
The Designer Eclipse Feature Should Be Separated Into A Design-Time
Feature And A Runtime-Time Feature
------------------------------------------------------------------------------------------------------
Key: TEIIDDES-261
URL: https://jira.jboss.org/jira/browse/TEIIDDES-261
Project: Teiid Designer
Issue Type: Task
Affects Versions: 7.0
Reporter: Dan Florian
Fix For: 7.0
A version of Teiid Designer should be available that does not include the ability to
perform data preview, connection management, and VDB execution. This design-time Designer
would be suited to users that are strictly data modelers. A "design-time only"
Designer would have a reduced footprint over the current Designer. Another Designer that
is more suited to users that test models and VDBs would then be needed. We would build
this Designer by adding on the data preview, connection management, and VDB execution
capabilities to the "design-time only" Designer. Eclipse features are the way
that different builds of the Designer can be accomplished.
We have done a pretty good job of isolating the data preview, connection management, and
VDB execution code into their own Eclipse plugins. The Eclipse plugins that were designed
to handle these capabilities are the dqp, dqp.ui, and sqlexplorer plugins. However, there
are a few cases of code found in "design-time only" plugins that depend on these
data preview, connection management, and VDB execution plugins. These cases will have to
be addressed in order to complete this task. Separate JIRAs should be written for these
cases as they are found and tied to this JIRA.
--
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
5:03 p.m.
New subject: [JBoss JIRA] Commented: (TEIIDDES-261) The Designer Eclipse Feature Should Be Separated Into A Design-Time Feature And A Runtime-Time Feature
[
https://jira.jboss.org/jira/browse/TEIIDDES-261?page=com.atlassian.jira.p...
]
John Verhaeg commented on TEIIDDES-261:
---------------------------------------
Separated UDF-related code out of DQP plug-ins into separate plug-ins so they can be used
by design-time-only version of Designer.
The Designer Eclipse Feature Should Be Separated Into A Design-Time
Feature And A Runtime-Time Feature
------------------------------------------------------------------------------------------------------
Key: TEIIDDES-261
URL: https://jira.jboss.org/jira/browse/TEIIDDES-261
Project: Teiid Designer
Issue Type: Task
Affects Versions: 7.0
Reporter: Dan Florian
Fix For: 7.0
A version of Teiid Designer should be available that does not include the ability to
perform data preview, connection management, and VDB execution. This design-time Designer
would be suited to users that are strictly data modelers. A "design-time only"
Designer would have a reduced footprint over the current Designer. Another Designer that
is more suited to users that test models and VDBs would then be needed. We would build
this Designer by adding on the data preview, connection management, and VDB execution
capabilities to the "design-time only" Designer. Eclipse features are the way
that different builds of the Designer can be accomplished.
We have done a pretty good job of isolating the data preview, connection management, and
VDB execution code into their own Eclipse plugins. The Eclipse plugins that were designed
to handle these capabilities are the dqp, dqp.ui, and sqlexplorer plugins. However, there
are a few cases of code found in "design-time only" plugins that depend on these
data preview, connection management, and VDB execution plugins. These cases will have to
be addressed in order to complete this task. Separate JIRAs should be written for these
cases as they are found and tied to this JIRA.
--
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
12:40 p.m.
New subject: [JBoss JIRA] Assigned: (TEIIDDES-261) The Designer Eclipse Feature Should Be Separated Into A Design-Time Feature And A Runtime-Time Feature
[
https://jira.jboss.org/jira/browse/TEIIDDES-261?page=com.atlassian.jira.p...
]
Barry LaFond reassigned TEIIDDES-261:
-------------------------------------
Assignee: Barry LaFond
The Designer Eclipse Feature Should Be Separated Into A Design-Time
Feature And A Runtime-Time Feature
------------------------------------------------------------------------------------------------------
Key: TEIIDDES-261
URL: https://jira.jboss.org/jira/browse/TEIIDDES-261
Project: Teiid Designer
Issue Type: Task
Affects Versions: 7.0
Reporter: Dan Florian
Assignee: Barry LaFond
Fix For: 7.0
A version of Teiid Designer should be available that does not include the ability to
perform data preview, connection management, and VDB execution. This design-time Designer
would be suited to users that are strictly data modelers. A "design-time only"
Designer would have a reduced footprint over the current Designer. Another Designer that
is more suited to users that test models and VDBs would then be needed. We would build
this Designer by adding on the data preview, connection management, and VDB execution
capabilities to the "design-time only" Designer. Eclipse features are the way
that different builds of the Designer can be accomplished.
We have done a pretty good job of isolating the data preview, connection management, and
VDB execution code into their own Eclipse plugins. The Eclipse plugins that were designed
to handle these capabilities are the dqp, dqp.ui, and sqlexplorer plugins. However, there
are a few cases of code found in "design-time only" plugins that depend on these
data preview, connection management, and VDB execution plugins. These cases will have to
be addressed in order to complete this task. Separate JIRAs should be written for these
cases as they are found and tied to this JIRA.
--
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
10 a.m.
New subject: [JBoss JIRA] Resolved: (TEIIDDES-261) The Designer Eclipse Feature Should Be Separated Into A Design-Time Feature And A Runtime-Time Feature
[
https://jira.jboss.org/browse/TEIIDDES-261?page=com.atlassian.jira.plugin...
]
Barry LaFond resolved TEIIDDES-261.
-----------------------------------
Resolution: Done
This is done. The JBoss Tools update site categories expose Designer in 2 parts,
design-time and run-time.
Code is also separated. VDB editing is basically a design-time exercise.
The Designer Eclipse Feature Should Be Separated Into A Design-Time
Feature And A Runtime-Time Feature
------------------------------------------------------------------------------------------------------
Key: TEIIDDES-261
URL: https://jira.jboss.org/browse/TEIIDDES-261
Project: Teiid Designer
Issue Type: Task
Affects Versions: 7.0
Reporter: Dan Florian
Assignee: Barry LaFond
Fix For: 7.0
A version of Teiid Designer should be available that does not include the ability to
perform data preview, connection management, and VDB execution. This design-time Designer
would be suited to users that are strictly data modelers. A "design-time only"
Designer would have a reduced footprint over the current Designer. Another Designer that
is more suited to users that test models and VDBs would then be needed. We would build
this Designer by adding on the data preview, connection management, and VDB execution
capabilities to the "design-time only" Designer. Eclipse features are the way
that different builds of the Designer can be accomplished.
We have done a pretty good job of isolating the data preview, connection management, and
VDB execution code into their own Eclipse plugins. The Eclipse plugins that were designed
to handle these capabilities are the dqp, dqp.ui, and sqlexplorer plugins. However, there
are a few cases of code found in "design-time only" plugins that depend on these
data preview, connection management, and VDB execution plugins. These cases will have to
be addressed in order to complete this task. Separate JIRAs should be written for these
cases as they are found and tied to this JIRA.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5305
days inactive
5436
days old
teiid-designer-issues@lists.jboss.org
4 comments
3 participants
participants (3)
-
Barry LaFond (JIRA) -
Dan Florian (JIRA)
-
John Verhaeg (JIRA)