November 2017 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-3097) Create common JNDI entry workflow requiring "java:/" prefix

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3097?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-3097: ----------------------------------- Fix Version/s: 11.1.1 > Create common JNDI entry workflow requiring "java:/" prefix > ----------------------------------------------------------- > > Key: TEIIDDES-3097 > URL: https://issues.jboss.org/browse/TEIIDDES-3097 > Project: Teiid Designer > Issue Type: Enhancement > Components: Datatools Integration, Editors, Teiid Integration > Affects Versions: 11.0.1 > Reporter: Barry LaFond > Fix For: 11.1, 11.1.1 > > Attachments: jdgConnectionProfile.png, webServiceJNDI.png > > > Change all JNDI name entry fields to validate using common validator to require proper "java:/" prefix and verify valid characters only after that. > This should collapse all possible JNDI text fields to operate with the same validation logic and make the "java:/" prefix a requirement rather than confusing the user in allowing a name without it yet adding it behind the scenes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3147) Import a REST service source and view model crashes

by Michael Echevarria (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3147?page=com.atlassian.jira.plu... ] Michael Echevarria commented on TEIIDDES-3147: ---------------------------------------------- The rest endpoint being used in the example that produced this bug is located here [https://jsonplaceholder.typicode.com/users|https://jsonplaceholder.typico...] The instructions being followed are these steps [http://redhatgov.io/workshops/jdv_dev/exercise6/|http://redhatgov.io/work...] > Import a REST service source and view model crashes > --------------------------------------------------- > > Key: TEIIDDES-3147 > URL: https://issues.jboss.org/browse/TEIIDDES-3147 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Usability > Affects Versions: 11.1 > Environment: JBoss Developer Studio 11, Teiid Designer 11.1 > Reporter: Michael Echevarria > Assignee: Barry LaFond > Priority: Critical > Fix For: 11.2 > > Attachments: rest-import-crash.mkv > > > When generating the source and view model on importing a web service, the designer will occasionally throw and error and fail the import -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3151) OData4 specific MXD is not found

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3151?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-3151: ---------------------------------------- [~blafond] The DDL is the one that defines all metadata *always*. If there are any archive specific properties like security, rest war generation those properties can be in the VDB level properties. The odata4.mxd is the custom mxd I tried to use in my workspace where I changed the namespace of the odata schema coming in from server (I simply used DDL based import, where I edited the namespace in the file) because I could not edit/modify the built-in odata.mxd. But as I noted in the previous comment, the odata v2 and odata v4 metadata from the server use exactly *SAME* namespace, that means the properties in odata.mxd need to be updated as opposed to creating a new namespace for odata v4. If you want you can add some comments in the description as to which property belongs to which version. Alternatively Teiid can create a new namespace for the odata v4, but that will be a break in compatibility, and previously created VDBs will no longer work. > OData4 specific MXD is not found > --------------------------------- > > Key: TEIIDDES-3151 > URL: https://issues.jboss.org/browse/TEIIDDES-3151 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 11.1 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Priority: Blocker > Fix For: 11.1.1 > > Attachments: odata4.mxd > > > While working on the case I found that there is no "odata4" specific MXD nor the current odata MXD is updated with newer properties for the V4. Since server uses the same namespace the current one needs to be updated. > A sample MXD (minus the namespace) is attached. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3147) Import a REST service source and view model crashes

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3147?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-3147: ---------------------------------------- [~mechevar] I tried a couple imports (weather wsdl etc) and it imported without error. If you catch it again, could you attach wsdl URL and error log. thx > Import a REST service source and view model crashes > --------------------------------------------------- > > Key: TEIIDDES-3147 > URL: https://issues.jboss.org/browse/TEIIDDES-3147 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Usability > Affects Versions: 11.1 > Environment: JBoss Developer Studio 11, Teiid Designer 11.1 > Reporter: Michael Echevarria > Assignee: Barry LaFond > Priority: Critical > Fix For: 11.2 > > Attachments: rest-import-crash.mkv > > > When generating the source and view model on importing a web service, the designer will occasionally throw and error and fail the import -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3147) Import a REST service source and view model crashes

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3147?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-3147: ----------------------------------- Fix Version/s: 11.2 (was: 11.1.1) > Import a REST service source and view model crashes > --------------------------------------------------- > > Key: TEIIDDES-3147 > URL: https://issues.jboss.org/browse/TEIIDDES-3147 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Usability > Affects Versions: 11.1 > Environment: JBoss Developer Studio 11, Teiid Designer 11.1 > Reporter: Michael Echevarria > Assignee: Barry LaFond > Priority: Critical > Fix For: 11.2 > > Attachments: rest-import-crash.mkv > > > When generating the source and view model on importing a web service, the designer will occasionally throw and error and fail the import -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3151) OData4 specific MXD is not found

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3151?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-3151: ---------------------------------------- [~rareddy] Is there anything that's in the *-vdb.xml/DDL OPTIONS() that indicates that the *teiid_odata* properties are *odata.mxd* versus *odata4.mxd* other than the property keys? > OData4 specific MXD is not found > --------------------------------- > > Key: TEIIDDES-3151 > URL: https://issues.jboss.org/browse/TEIIDDES-3151 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 11.1 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Priority: Blocker > Fix For: 11.1.1 > > Attachments: odata4.mxd > > > While working on the case I found that there is no "odata4" specific MXD nor the current odata MXD is updated with newer properties for the V4. Since server uses the same namespace the current one needs to be updated. > A sample MXD (minus the namespace) is attached. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3150) Teiid Connection Importer - Provide a way to refresh the existing "datasources"

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3150?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-3150: ---------------------------------------- Note that this request was to provide refresh on the "Teiid Connection importer" since I could not create a data source because of TEIIDDES-3149, I created manually but there was no way on this screen to see the updated one. Anyway, this is an enhancement, so I leave it up to your discretion to implement or reject it as there are other means to accomplish the same. > Teiid Connection Importer - Provide a way to refresh the existing "datasources" > -------------------------------------------------------------------------------- > > Key: TEIIDDES-3150 > URL: https://issues.jboss.org/browse/TEIIDDES-3150 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 11.1 > Reporter: Ramesh Reddy > > Currently, there is no way to refresh the available data sources in the Teiid Connection Importer unless the user goes to Servers tab, and disconnects and reconnects. There needs to a way refresh or just latest data sources when this wizard is invoked. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3152) VDB does not have MXD based properties

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3152?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-3152: -------------------------------------- Assignee: Barry LaFond > VDB does not have MXD based properties > -------------------------------------- > > Key: TEIIDDES-3152 > URL: https://issues.jboss.org/browse/TEIIDDES-3152 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 11.1 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Priority: Blocker > Fix For: 11.1.1 > > Attachments: sample.ddl > > > After adding a custom MXD (see TEIIDDES-3151), if you import a DDL that makes use of the MXD properties, the model will show the properties in "Extensions" in left side panel. However, when creating a .vdb or dynamic VDB these properties not exported at all in the resulting VDB > Attached a sample DDL file, but same would apply if I use Teiid Connection Importer too. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3152) VDB does not have MXD based properties

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3152?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-3152: ----------------------------------- Fix Version/s: 11.1.1 > VDB does not have MXD based properties > -------------------------------------- > > Key: TEIIDDES-3152 > URL: https://issues.jboss.org/browse/TEIIDDES-3152 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 11.1 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Priority: Blocker > Fix For: 11.1.1 > > Attachments: sample.ddl > > > After adding a custom MXD (see TEIIDDES-3151), if you import a DDL that makes use of the MXD properties, the model will show the properties in "Extensions" in left side panel. However, when creating a .vdb or dynamic VDB these properties not exported at all in the resulting VDB > Attached a sample DDL file, but same would apply if I use Teiid Connection Importer too. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3151) OData4 specific MXD is not found

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3151?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-3151: -------------------------------------- Assignee: Barry LaFond > OData4 specific MXD is not found > --------------------------------- > > Key: TEIIDDES-3151 > URL: https://issues.jboss.org/browse/TEIIDDES-3151 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 11.1 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Priority: Blocker > Fix For: 11.1.1 > > Attachments: odata4.mxd > > > While working on the case I found that there is no "odata4" specific MXD nor the current odata MXD is updated with newer properties for the V4. Since server uses the same namespace the current one needs to be updated. > A sample MXD (minus the namespace) is attached. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 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 November 2017