[JBoss JIRA] (TEIIDDES-2258) Annotate VDB's in Model Explorer if deployed to default server and if VDB DS exists
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-2258:
--------------------------------------
Summary: Annotate VDB's in Model Explorer if deployed to default server and if VDB DS exists
Key: TEIIDDES-2258
URL: https://issues.jboss.org/browse/TEIIDDES-2258
Project: Teiid Designer
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: VDB & Execution
Reporter: Barry LaFond
Would be beneficial to see whether or not a VDB is already deployed on the default server and whether a VDB data source has been created/deployed.e
1) Note a VDB DS JNDI name does not have to match the VDB name, so matching it to the VDB will require looking at the VDB name in the URI.
2) Maybe decorate the VDB with a small server image and a small ds-related image.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 3 months
[JBoss JIRA] (TEIIDDES-2257) Create VDB DataSource Dialog Enhancements
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2257?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2257:
----------------------------------------
Adding the VDB DS JNDI name text field and boolean check box would require adding properties to the vdb.xml manifest, however, I'm thinking users would want to still override the DS at deployment time anyway.
So I'm in favor of adding a check for existing DS and ask the user to override or not (YES or NO).
> Create VDB DataSource Dialog Enhancements
> -----------------------------------------
>
> Key: TEIIDDES-2257
> URL: https://issues.jboss.org/browse/TEIIDDES-2257
> Project: Teiid Designer
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Usability
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Fix For: 8.6, 8.5.1
>
> Attachments: create-vdb-data-source-in-server-view.png, ds.png
>
>
> 1) The dialog shows "OK" and "Cancel" buttons, they need to be "yes" or "no" buttons.
> 2) If the data source is already available in server, then do not ask the user if they want to create it again.
> Even better is, ask on the vdb-explorer window to enter (pre-fill) the JNDI name, with a check-box to create or not, rather than asking at later time. No annoying pop-up dialog.
> Plus Points: To be useful, provide right click on VDB in server panel and create a Data source.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 3 months
[JBoss JIRA] (TEIIDDES-2256) Confusing data type "integer" and "int"
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2256?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2256:
----------------------------------------
{code:xml}
<xs:simpleType mmedt:UUID="mmuuid:822b9a40-a066-1e26-9b08-d6079ebe1f0d" mmedt:runtimeDataType="biginteger" mmedt:runtimeDataTypeFixed="false" name="biginteger">
<xs:annotation>
<xs:appinfo/>
<xs:documentation>[Definition:] biginteger represent
arbitrary-precision integers. All operations behave as
if bigintegers were represented in two's-complement
notation (like Java's primitive integer types).</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:decimal"/>
</xs:simpleType>
{code}
> Confusing data type "integer" and "int"
> ---------------------------------------
>
> Key: TEIIDDES-2256
> URL: https://issues.jboss.org/browse/TEIIDDES-2256
> Project: Teiid Designer
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Ramesh Reddy
>
> I understand that
> "integer" maps to "xs:biginteger"
> "int" maps "xs:long"
> How they are confusing when there is already one available for biginteger. Also the Table creation wizard does not provide option to to select "int". When user chooses "integer" it often is "int".
> This confusion needs to be resolved. IMO "integer" can be removed, however I am not sure how it effects data type system
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 3 months
[JBoss JIRA] (TEIIDDES-2257) Create VDB DataSource Dialog Enhancements
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2257?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2257:
-----------------------------------
Attachment: create-vdb-data-source-in-server-view.png
> Create VDB DataSource Dialog Enhancements
> -----------------------------------------
>
> Key: TEIIDDES-2257
> URL: https://issues.jboss.org/browse/TEIIDDES-2257
> Project: Teiid Designer
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Usability
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Fix For: 8.6, 8.5.1
>
> Attachments: create-vdb-data-source-in-server-view.png, ds.png
>
>
> 1) The dialog shows "OK" and "Cancel" buttons, they need to be "yes" or "no" buttons.
> 2) If the data source is already available in server, then do not ask the user if they want to create it again.
> Even better is, ask on the vdb-explorer window to enter (pre-fill) the JNDI name, with a check-box to create or not, rather than asking at later time. No annoying pop-up dialog.
> Plus Points: To be useful, provide right click on VDB in server panel and create a Data source.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 3 months
[JBoss JIRA] (TEIIDDES-2257) Create VDB DataSource Dialog Enhancements
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2257?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2257:
-----------------------------------
Attachment: (was: create-relational-native-query-procedure-result-set-panel.png)
> Create VDB DataSource Dialog Enhancements
> -----------------------------------------
>
> Key: TEIIDDES-2257
> URL: https://issues.jboss.org/browse/TEIIDDES-2257
> Project: Teiid Designer
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Usability
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Fix For: 8.6, 8.5.1
>
> Attachments: create-vdb-data-source-in-server-view.png, ds.png
>
>
> 1) The dialog shows "OK" and "Cancel" buttons, they need to be "yes" or "no" buttons.
> 2) If the data source is already available in server, then do not ask the user if they want to create it again.
> Even better is, ask on the vdb-explorer window to enter (pre-fill) the JNDI name, with a check-box to create or not, rather than asking at later time. No annoying pop-up dialog.
> Plus Points: To be useful, provide right click on VDB in server panel and create a Data source.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 3 months
[JBoss JIRA] (TEIIDDES-2194) On windows, when deploying VDB, and data source exist, it still wants to create datasource
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2194?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2194:
-----------------------------------
Fix Version/s: 8.6
> On windows, when deploying VDB, and data source exist, it still wants to create datasource
> ------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2194
> URL: https://issues.jboss.org/browse/TEIIDDES-2194
> Project: Teiid Designer
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: VDB & Execution
> Affects Versions: 8.4
> Environment: Windows 2008 for designer and server (same box)
> 8.4 final for designer and DV 6.1
> Reporter: Van Halbert
> Fix For: 8.6
>
> Attachments: image.png
>
>
> When deploying VDB and the data source already exist, it still want to create a new data source. see attachment.
> The default was left, just to move on. The test datasource was created, but the VDB still worked, because the JNDI in the VDB was mapped to an already configured datasource.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 3 months
[JBoss JIRA] (TEIIDDES-2194) On windows, when deploying VDB, and data source exist, it still wants to create datasource
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2194?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2194:
-----------------------------------
Fix Version/s: 8.5.1
> On windows, when deploying VDB, and data source exist, it still wants to create datasource
> ------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2194
> URL: https://issues.jboss.org/browse/TEIIDDES-2194
> Project: Teiid Designer
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: VDB & Execution
> Affects Versions: 8.4
> Environment: Windows 2008 for designer and server (same box)
> 8.4 final for designer and DV 6.1
> Reporter: Van Halbert
> Fix For: 8.6, 8.5.1
>
> Attachments: image.png
>
>
> When deploying VDB and the data source already exist, it still want to create a new data source. see attachment.
> The default was left, just to move on. The test datasource was created, but the VDB still worked, because the JNDI in the VDB was mapped to an already configured datasource.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 3 months
[JBoss JIRA] (TEIIDDES-2195) Unable to add View model to VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2195?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2195.
------------------------------------
Assignee: Barry LaFond
Resolution: Out of Date
> Unable to add View model to VDB
> -------------------------------
>
> Key: TEIIDDES-2195
> URL: https://issues.jboss.org/browse/TEIIDDES-2195
> Project: Teiid Designer
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: VDB & Execution
> Affects Versions: 8.4
> Reporter: Van Halbert
> Assignee: Barry LaFond
>
> Create a VDB that contained the source model. Deployed and tested. Then created a View model that has the existing source model as a dependency. Then went to the VDB editor and clicked to add a model. Selected the View model to add, but wouldn't allow because the there's a duplicate.
> Had to first remove the source model from the VDB editor, save, then go in and add the View model (which then added the source model dependency).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 3 months
[JBoss JIRA] (TEIIDDES-2231) Rename "Mapped Role Names" to "Mapped Enterprise Groups"
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2231?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2231:
-----------------------------------
Fix Version/s: 8.6
Assignee: Barry LaFond
> Rename "Mapped Role Names" to "Mapped Enterprise Groups"
> --------------------------------------------------------
>
> Key: TEIIDDES-2231
> URL: https://issues.jboss.org/browse/TEIIDDES-2231
> Project: Teiid Designer
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Usability
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Fix For: 8.6
>
>
> Data Roles dialog box shows "Mapped Role Names" as name to map the data-roles to enterprise groups. Talking with couple people I realized that, users are not readily able to grasp two concepts of mapping data-role name with enterprise groups.
> If the name is changed to "Mapped Enterprise Group" then it will little bit more clear about the intention. Also, if we can add a description like,
> "One to one mapping of a enterprise group of the logged in user based on JAAS authentication on the server"
> that would be informational.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 3 months