[JBoss JIRA] (TEIIDDES-2812) Add ability to reverse engineer into a Pojo object from a table or view
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2812?page=com.atlassian.jira.plu... ]
Van Halbert edited comment on TEIIDDES-2812 at 8/24/16 10:13 AM:
-----------------------------------------------------------------
Need a couple additions to this, as these came about after the initial design work was done.
- When creating materialized table, create a duplicate copy (for staging), but prefixing the name with "ST_"
- need to create/add a medata extension property to the staging table.
Also, as had been previous discussed, is the creation a connection profile for JDG.
Settings:
- JNDI Name
- cacheTypeMap where the format is:
cacheName:className[;pkFieldName[:cacheKeyJavaType]]
cacheName = name of the primary cache in JDG
className = pojo class name for the object stored in JDG (this would be class of the pojo created)
pkFieldName = name of the attribute that is identified as the key value to the object stored in the JDG cache map (key=value)
cacheKeyJavaType = [optional] java type of the pkFieldName when its java type of the key value is different from its pojo attribute java type
- How to connect to JDG
a. CacheJndiName - find cache using JNDI
b. RemoteServerList - Server list, specify 1 or more host:port[,host:port] to connect to
c. HotRodClientPropertiesFile - HotRod client properties file
- Being using for materialization
a. StagingCacheName - jdg cache used for staging
b. AliasCacheName - JDG cache used for storing/tracking cache aliasing (can be shared for all JDG materializations)
was (Author: van.halbert):
Need a couple additions to this, as these came about after the initial design work was done.
- When creating materialized table, create a duplicate copy (for staging), but prefixing the name with "ST_"
- need to create/add a medata extension property to the staging table.
Also, as had been previous discussed, is the creation a connection profile for JDG.
Settings:
- JNDI Name
- cacheTypeMap where the format is:
cacheName:className[;pkFieldName[:cacheKeyJavaType]]
cacheName = name of the primary cache in JDG
className = pojo class name for the object stored in JDG
pkFieldName = name of the attribute that is identified as the key value to the object stored in the JDG cache map (key=value)
cacheKeyJavaType = [optional] java type of the pkFieldName when its java type of the key value is different from its pojo attribute java type
- How to connect to JDG
a. CacheJndiName - find cache using JNDI
b. RemoteServerList - Server list, specify 1 or more host:port[,host:port] to connect to
c. HotRodClientPropertiesFile - HotRod client properties file
- Being using for materialization
a. StagingCacheName - jdg cache used for staging
b. AliasCacheName - JDG cache used for storing/tracking cache aliasing (can be shared for all JDG materializations)
> 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: Infinispan_Materialization.mxd, 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, 1 month
[JBoss JIRA] (TEIIDDES-2812) Add ability to reverse engineer into a Pojo object from a table or view
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2812?page=com.atlassian.jira.plu... ]
Van Halbert commented on TEIIDDES-2812:
---------------------------------------
When the source model is created for the materialized tables, can the following translator overrides be set on the model so that when the VDB is created, they are applied:
<property name="SupportsDirectQueryProcedure" value="true"/>
<property name="SupportsNativeQueries" value="true"/>
> 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: Infinispan_Materialization.mxd, 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, 1 month
[JBoss JIRA] (TEIIDDES-2812) Add ability to reverse engineer into a Pojo object from a table or view
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2812?page=com.atlassian.jira.plu... ]
Van Halbert updated TEIIDDES-2812:
----------------------------------
Attachment: Infinispan_Materialization.mxd
This is an example of the MED that will need to be added.
When the staging table is created, the value needs to be assigned the name of the primary table.
> 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: Infinispan_Materialization.mxd, 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, 1 month
[JBoss JIRA] (TEIIDDES-2812) Add ability to reverse engineer into a Pojo object from a table or view
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2812?page=com.atlassian.jira.plu... ]
Van Halbert commented on TEIIDDES-2812:
---------------------------------------
Need a couple additions to this, as these came about after the initial design work was done.
- When creating materialized table, create a duplicate copy (for staging), but prefixing the name with "ST_"
- need to create/add a medata extension property to the staging table.
Also, as had been previous discussed, is the creation a connection profile for JDG.
Settings:
- JNDI Name
- cacheTypeMap where the format is:
cacheName:className[;pkFieldName[:cacheKeyJavaType]]
cacheName = name of the primary cache in JDG
className = pojo class name for the object stored in JDG
pkFieldName = name of the attribute that is identified as the key value to the object stored in the JDG cache map (key=value)
cacheKeyJavaType = [optional] java type of the pkFieldName when its java type of the key value is different from its pojo attribute java type
- How to connect to JDG
a. CacheJndiName - find cache using JNDI
b. RemoteServerList - Server list, specify 1 or more host:port[,host:port] to connect to
c. HotRodClientPropertiesFile - HotRod client properties file
- Being using for materialization
a. StagingCacheName - jdg cache used for staging
b. AliasCacheName - JDG cache used for storing/tracking cache aliasing (can be shared for all JDG materializations)
> 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, 1 month
[JBoss JIRA] (TEIIDDES-2895) No warning after deleting schema and UDF Jars
by Mario Majernik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2895?page=com.atlassian.jira.plu... ]
Mario Majernik updated TEIIDDES-2895:
-------------------------------------
Description:
There is no warning after deleting schema which is used by models. VDB is deployed without warnings. Following query fails on missing schema.
Should be there some warning that schema was deleted and VDB should not be deploy on server without schema.
EDIT: The same thing with UDF Jars. No warning after deleting but VDB is corrupt after deploying on server.
was:
There is no warning after deleting schema which is used by models. VDB is deployed without warnings. Following query fails on missing schema.
Should be there some warning that schema was deleted and VDB should not be deploy on server without schema.
Summary: No warning after deleting schema and UDF Jars (was: No warning after deleting schema )
> No warning after deleting schema and UDF Jars
> ---------------------------------------------
>
> Key: TEIIDDES-2895
> URL: https://issues.jboss.org/browse/TEIIDDES-2895
> Project: Teiid Designer
> Issue Type: Bug
> Components: Editors
> Affects Versions: 10.0.1
> Reporter: Mario Majernik
> Attachments: ScreenShot1.png, XmlStagingTableProject.zip
>
>
> There is no warning after deleting schema which is used by models. VDB is deployed without warnings. Following query fails on missing schema.
> Should be there some warning that schema was deleted and VDB should not be deploy on server without schema.
> EDIT: The same thing with UDF Jars. No warning after deleting but VDB is corrupt after deploying on server.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (TEIIDDES-2532) 1024 x 768 - Reconciler - not all buttons are visible
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2532?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-2532.
----------------------------------
> 1024 x 768 - Reconciler - not all buttons are visible
> -----------------------------------------------------
>
> Key: TEIIDDES-2532
> URL: https://issues.jboss.org/browse/TEIIDDES-2532
> Project: Teiid Designer
> Issue Type: Bug
> Components: Transformations
> Affects Versions: 9.0.2
> Environment: Mac OS X
> Reporter: Matus Makovy
> Assignee: Barry LaFond
> Fix For: 9.1, 8.6.2 Beta1, 8.6.2
>
> Attachments: Screen Shot 2015-05-19 at 1.32.08 PM.png, Screen Shot 2015-05-19 at 1.32.19 PM.png, Screen Shot 2015-05-19 at 1.32.41 PM.png, Screen Shot 2015-05-19 at 1.32.49 PM.png
>
>
> I can not see all buttons in reconciler when it opens. Type resolver button is completely hidden.
> This problem is also in Type resolver dialogue.
> User can enlarge the window and the button will show, but when the dialogue opens user doesn't know that there is Type resolver button.
> Screenshots attached
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month