July 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2232) Cannot create JDBC/Oracle connection profile using ServiceName syntax

by Tom Johnston (JIRA)

Tom Johnston created TEIIDDES-2232: -------------------------------------- Summary: Cannot create JDBC/Oracle connection profile using ServiceName syntax Key: TEIIDDES-2232 URL: https://issues.jboss.org/browse/TEIIDDES-2232 Project: Teiid Designer Issue Type: Bug Security Level: Public (Everyone can see) Components: Teiid Integration Affects Versions: 8.4 Reporter: Tom Johnston Cannot successfully create a jdbc url like: "jdbc:oracle:thin:scott/tiger@//myhost:1521/myservicename" which is found here: http://docs.oracle.com/cd/B14117_01/java.101/b10979/urls.htm Note the "../myservicename" -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2229) Merge various fixes from master into 8.5.1

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2229?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-2229: -------------------------------- Description: *Candidates* TEIIDDES-2224 web service returns 500 when concurrent access TEIIDDES-2218 JBossWS-CXF/RestEasy WAR menu options are impl specific TEIIDDES-2188 Move the REST Importer out of the XML Importer and into a Separate Importer Option *Completed Upstream* TEIIDDES-#### <title> was: *Candidates* TEIIDDES-2224 web service returns 500 when concurrent access TEIIDDES-2218 JBossWS-CXF/RestEasy WAR menu options are impl specific *Completed Upstream* TEIIDDES-#### <title> > Merge various fixes from master into 8.5.1 > ------------------------------------------ > > Key: TEIIDDES-2229 > URL: https://issues.jboss.org/browse/TEIIDDES-2229 > Project: Teiid Designer > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 8.5.1 > Reporter: Ted Jones > Assignee: Johnathon Lee > Priority: Blocker > Fix For: 8.5.1 > > > *Candidates* > TEIIDDES-2224 web service returns 500 when concurrent access > TEIIDDES-2218 JBossWS-CXF/RestEasy WAR menu options are impl specific > TEIIDDES-2188 Move the REST Importer out of the XML Importer and into a Separate Importer Option > *Completed Upstream* > TEIIDDES-#### <title> -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2188) Move the REST Importer out of the XML Importer and into a Separate Importer Option

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2188?page=com.atlassian.jira.plu... ] Ted Jones resolved TEIIDDES-2188. --------------------------------- Resolution: Done > Move the REST Importer out of the XML Importer and into a Separate Importer Option > ---------------------------------------------------------------------------------- > > Key: TEIIDDES-2188 > URL: https://issues.jboss.org/browse/TEIIDDES-2188 > Project: Teiid Designer > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Documentation, Import/Export, Web Services Support > Affects Versions: 8.5 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 8.5.1 > > Attachments: importersREST.png > > > Currently the REST importer is included in the XML importer. It should be moved to it's own import option (like SOAP) to make it more obvious. Also, since we are adding JSON support for REST services as sources in Designer, REST won't just be for XML anymore. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2188) Move the REST Importer out of the XML Importer and into a Separate Importer Option

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2188?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-2188: -------------------------------- Git Pull Request: https://github.com/Teiid-Designer/teiid-designer/pull/381 > Move the REST Importer out of the XML Importer and into a Separate Importer Option > ---------------------------------------------------------------------------------- > > Key: TEIIDDES-2188 > URL: https://issues.jboss.org/browse/TEIIDDES-2188 > Project: Teiid Designer > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Documentation, Import/Export, Web Services Support > Affects Versions: 8.5 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 8.5.1 > > Attachments: importersREST.png > > > Currently the REST importer is included in the XML importer. It should be moved to it's own import option (like SOAP) to make it more obvious. Also, since we are adding JSON support for REST services as sources in Designer, REST won't just be for XML anymore. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2209) anytime view models are created (I.e. DDL import as View) allow checkbox to make default transformation so that the model is deployable

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2209?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2209. ------------------------------------ Resolution: Done Done > anytime view models are created (I.e. DDL import as View) allow checkbox to make default transformation so that the model is deployable > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2209 > URL: https://issues.jboss.org/browse/TEIIDDES-2209 > Project: Teiid Designer > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Import/Export > Reporter: Tom Johnston > Assignee: Barry LaFond > Fix For: 8.6 > > Attachments: ddl-importer-page-1.png, order_test_ddl.txt > > > I have mentioned this before but now that DDL import can generate view models (the only mechanism I can see to bring in logical/conceptual models from other tools like PowerDesigner etc) > If the model is successful in that it brings all components it is still not a valid model to deploy to a vdb and start work against. > My proposal is to generate SQL using the column metadata for the view itself. > For example... I've attached a simple ddl but for order_header it'd be like: > SELECT null AS Order_header_id, null AS order_header_name > The primary purpose is to make the model deploy-able immediately. > I'd also like to see this 'feature' at the Model-->Generate stubs when right clicking the model. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2209) anytime view models are created (I.e. DDL import as View) allow checkbox to make default transformation so that the model is deployable

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2209?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2209: ----------------------------------- Attachment: ddl-importer-page-1.png re-worked DDL Importer page 1 which includes new "groups" of widgets and an added checkbox to generate default SQL. > anytime view models are created (I.e. DDL import as View) allow checkbox to make default transformation so that the model is deployable > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2209 > URL: https://issues.jboss.org/browse/TEIIDDES-2209 > Project: Teiid Designer > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Import/Export > Reporter: Tom Johnston > Assignee: Barry LaFond > Fix For: 8.6 > > Attachments: ddl-importer-page-1.png, order_test_ddl.txt > > > I have mentioned this before but now that DDL import can generate view models (the only mechanism I can see to bring in logical/conceptual models from other tools like PowerDesigner etc) > If the model is successful in that it brings all components it is still not a valid model to deploy to a vdb and start work against. > My proposal is to generate SQL using the column metadata for the view itself. > For example... I've attached a simple ddl but for order_header it'd be like: > SELECT null AS Order_header_id, null AS order_header_name > The primary purpose is to make the model deploy-able immediately. > I'd also like to see this 'feature' at the Model-->Generate stubs when right clicking the model. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2188) Move the REST Importer out of the XML Importer and into a Separate Importer Option

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2188?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-2188: -------------------------------- Attachment: importersREST.png Added new importer option: *Web Service Source >> Source and View Model (REST)* Also renamed the SOAP importer: *Web Service Source >> Source and View Model (SOAP)* so the importers would display next to each other. See screenshot. > Move the REST Importer out of the XML Importer and into a Separate Importer Option > ---------------------------------------------------------------------------------- > > Key: TEIIDDES-2188 > URL: https://issues.jboss.org/browse/TEIIDDES-2188 > Project: Teiid Designer > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Documentation, Import/Export, Web Services Support > Affects Versions: 8.5 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 8.5.1 > > Attachments: importersREST.png > > > Currently the REST importer is included in the XML importer. It should be moved to it's own import option (like SOAP) to make it more obvious. Also, since we are adding JSON support for REST services as sources in Designer, REST won't just be for XML anymore. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2209) anytime view models are created (I.e. DDL import as View) allow checkbox to make default transformation so that the model is deployable

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2209?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2209: -------------------------------------- Assignee: Barry LaFond > anytime view models are created (I.e. DDL import as View) allow checkbox to make default transformation so that the model is deployable > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2209 > URL: https://issues.jboss.org/browse/TEIIDDES-2209 > Project: Teiid Designer > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Import/Export > Reporter: Tom Johnston > Assignee: Barry LaFond > Fix For: 8.6 > > Attachments: order_test_ddl.txt > > > I have mentioned this before but now that DDL import can generate view models (the only mechanism I can see to bring in logical/conceptual models from other tools like PowerDesigner etc) > If the model is successful in that it brings all components it is still not a valid model to deploy to a vdb and start work against. > My proposal is to generate SQL using the column metadata for the view itself. > For example... I've attached a simple ddl but for order_header it'd be like: > SELECT null AS Order_header_id, null AS order_header_name > The primary purpose is to make the model deploy-able immediately. > I'd also like to see this 'feature' at the Model-->Generate stubs when right clicking the model. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2231) Rename "Mapped Role Names" to "Mapped Enterprise Groups"

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2231?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2231: ---------------------------------------- We can even try "Mapped Enterprise Role/Group" > 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 > > 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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2231) Rename "Mapped Role Names" to "Mapped Enterprise Groups"

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2231?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2231: ---------------------------------------- What is in the XML does not matter, it is not viewed by the user. I will update the Teiid Console/Doc. It is not documentation that is superior, it is common user terminology that users use. We would need to fix all the places to be consistent. > 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 > > 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

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2014