[JBoss JIRA] (TEIIDDES-2902) Deprecate XML Document Models
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2902?page=com.atlassian.jira.plu... ]
Steven Hawkins reassigned TEIIDDES-2902:
----------------------------------------
Assignee: (was: Steven Hawkins)
> Deprecate XML Document Models
> -----------------------------
>
> Key: TEIIDDES-2902
> URL: https://issues.jboss.org/browse/TEIIDDES-2902
> Project: Teiid Designer
> Issue Type: Task
> Reporter: Steven Hawkins
>
> With TEIID-4100 our OData v4 implementation provides most of the features provided by XML Document models. Between OData and SQL/XML as replacements, we need to formally deprecate the legacy XML approach.
> Additional tasks include:
> A way to perform OData queries from within the vdb
> Optimizations to approximate the usage of staging tables
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIIDDES-2902) Deprecate XML Document Models
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2902?page=com.atlassian.jira.plu... ]
Steven Hawkins updated TEIIDDES-2902:
-------------------------------------
Component/s: Modeling
Description: With TEIID-4100 our OData v4 implementation provides most of the features provided by XML Document models. Between OData and SQL/XML as replacements, we need to formally deprecate the legacy XML approach. (was: With TEIID-4100 our OData v4 implementation provides most of the features provided by XML Document models. Between OData and SQL/XML as replacements, we need to formally deprecate the legacy XML approach.
Additional tasks include:
A way to perform OData queries from within the vdb
Optimizations to approximate the usage of staging tables )
> Deprecate XML Document Models
> -----------------------------
>
> Key: TEIIDDES-2902
> URL: https://issues.jboss.org/browse/TEIIDDES-2902
> Project: Teiid Designer
> Issue Type: Task
> Components: Modeling
> Reporter: Steven Hawkins
>
> With TEIID-4100 our OData v4 implementation provides most of the features provided by XML Document models. Between OData and SQL/XML as replacements, we need to formally deprecate the legacy XML approach.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIIDDES-2902) Deprecate XML Document Models
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2902?page=com.atlassian.jira.plu... ]
Steven Hawkins moved TEIID-4401 to TEIIDDES-2902:
-------------------------------------------------
Project: Teiid Designer (was: Teiid)
Key: TEIIDDES-2902 (was: TEIID-4401)
Component/s: (was: Query Engine)
Fix Version/s: (was: 9.1)
> Deprecate XML Document Models
> -----------------------------
>
> Key: TEIIDDES-2902
> URL: https://issues.jboss.org/browse/TEIIDDES-2902
> Project: Teiid Designer
> Issue Type: Task
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
>
> With TEIID-4100 our OData v4 implementation provides most of the features provided by XML Document models. Between OData and SQL/XML as replacements, we need to formally deprecate the legacy XML approach.
> Additional tasks include:
> A way to perform OData queries from within the vdb
> Optimizations to approximate the usage of staging tables
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIIDDES-2812) Add ability to reverse engineer into a Pojo object from a table or view
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2812?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2812.
------------------------------------
Resolution: Done
Done
> Add ability to reverse engineer into a Pojo object from a table or view
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-2812
> URL: https://issues.jboss.org/browse/TEIIDDES-2812
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling, Usability
> Affects Versions: 9.0.6
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 10.0.2
>
> Attachments: jdg-module-generated-files.png, materialize-action.png, materialize-wizard-page-1.png, materialize-wizard-page-2.png, materialized-table-property-value.png
>
>
> The scenario is: select table/view, right mouse click select Create Pojo, present dialog, need a file chooser to select location to save output.
> Label of action: Create Pojo (or something to indicates the process)
> Dialog title: Create Pojo from Table [tableName]
> Message: This will create a Pojo class, and packaged in a jar, that is meant to be used when JDG will be used in materialization or accessed as a data source.
> Options:
> - file chooser option to select folder to save pojo jar
> - drop-down: <select option>
> Access JDG in Library Mode
> Access JDG via Hot Rod Client
> - pojo package name (default = org.teiid.pojo)
> - pojo jar name (default = pojo.jar)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIIDDES-2812) Add ability to reverse engineer into a Pojo object from a table or view
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2812?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2812:
----------------------------------------
10.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/3691ad7443e6d9bf9...
> Add ability to reverse engineer into a Pojo object from a table or view
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-2812
> URL: https://issues.jboss.org/browse/TEIIDDES-2812
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling, Usability
> Affects Versions: 9.0.6
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 10.0.2
>
> Attachments: jdg-module-generated-files.png, materialize-action.png, materialize-wizard-page-1.png, materialize-wizard-page-2.png, materialized-table-property-value.png
>
>
> The scenario is: select table/view, right mouse click select Create Pojo, present dialog, need a file chooser to select location to save output.
> Label of action: Create Pojo (or something to indicates the process)
> Dialog title: Create Pojo from Table [tableName]
> Message: This will create a Pojo class, and packaged in a jar, that is meant to be used when JDG will be used in materialization or accessed as a data source.
> Options:
> - file chooser option to select folder to save pojo jar
> - drop-down: <select option>
> Access JDG in Library Mode
> Access JDG via Hot Rod Client
> - pojo package name (default = org.teiid.pojo)
> - pojo jar name (default = pojo.jar)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months