December 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2409) Cannot set Content via Element in Webservice operation input and output

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2409?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-2409: ---------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1174648 > Cannot set Content via Element in Webservice operation input and output > ----------------------------------------------------------------------- > > Key: TEIIDDES-2409 > URL: https://issues.jboss.org/browse/TEIIDDES-2409 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling, Web Services Support > Affects Versions: 9.0.1 > Reporter: Andrej Šmigala > Attachments: ContentViaElementProject.zip > > > When trying to set Content via element for a web service operation input or output, the list of available elements is empty, even when there are XML Schema models in the project. > Windows, Linux > JBDS 8.0.1 GA > Designer 9.0.1 Beta2 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2409) Cannot set Content via Element in Webservice operation input and output

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2409?page=com.atlassian.jira.plu... ] Andrej Šmigala updated TEIIDDES-2409: ------------------------------------- Attachment: ContentViaElementProject.zip > Cannot set Content via Element in Webservice operation input and output > ----------------------------------------------------------------------- > > Key: TEIIDDES-2409 > URL: https://issues.jboss.org/browse/TEIIDDES-2409 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling, Web Services Support > Affects Versions: 9.0.1 > Reporter: Andrej Šmigala > Attachments: ContentViaElementProject.zip > > > When trying to set Content via element for a web service operation input or output, the list of available elements is empty, even when there are XML Schema models in the project. > Windows, Linux > JBDS 8.0.1 GA > Designer 9.0.1 Beta2 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2409) Cannot set Content via Element in Webservice operation input and output

by Andrej Šmigala (JIRA)

Andrej Šmigala created TEIIDDES-2409: ---------------------------------------- Summary: Cannot set Content via Element in Webservice operation input and output Key: TEIIDDES-2409 URL: https://issues.jboss.org/browse/TEIIDDES-2409 Project: Teiid Designer Issue Type: Bug Components: Modeling, Web Services Support Affects Versions: 9.0.1 Reporter: Andrej Šmigala When trying to set Content via element for a web service operation input or output, the list of available elements is empty, even when there are XML Schema models in the project. Windows, Linux JBDS 8.0.1 GA Designer 9.0.1 Beta2 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2348) Ctrl+v in Transformation editor pastes twice

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2348?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2348: --------------------------------------------------- asmigala(a)redhat.com changed the Status of [bug 1145633|https://bugzilla.redhat.com/show_bug.cgi?id=1145633] from ON_QA to VERIFIED > Ctrl+v in Transformation editor pastes twice > -------------------------------------------- > > Key: TEIIDDES-2348 > URL: https://issues.jboss.org/browse/TEIIDDES-2348 > Project: Teiid Designer > Issue Type: Bug > Components: Editors, Transformations > Affects Versions: 8.6.1 > Environment: JBDS 8.0.0.CR1 > Teiid Designer 8.6.1.Alpha1 > Windows, Linux > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Fix For: 9.0, 8.6.1, 9.0.1 > > > When hitting ctrl+v in Transformation editor, the text in clipboard is pasted twice. Does not happen when right-clicking and selecting paste. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2352) JDBC password lost after restart

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2352?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2352: --------------------------------------------------- asmigala(a)redhat.com changed the Status of [bug 1145756|https://bugzilla.redhat.com/show_bug.cgi?id=1145756] from ON_QA to VERIFIED > JDBC password lost after restart > -------------------------------- > > Key: TEIIDDES-2352 > URL: https://issues.jboss.org/browse/TEIIDDES-2352 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.6.1 > Environment: JBDS 8.0.0.CR1 > Teiid Designer 8.6.1.Alpha1 > Windows, Linux > Reporter: Andrej Šmigala > Assignee: Paul Richardson > Fix For: 9.0, 8.6.1 > > > The password for JDBC connection to Teiid server is reset every time JBDS is started -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2401) Add support exporting the Designer VDB as Dynamic VDB

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2401?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2401: ---------------------------------------- >So if a user is using * file,database, a git repo or combination of all* for their artifact, are they using multiple tools to make this happen and what are they? In the Teiid code, the metadata repository is a pluggable concept. A user can write their own metadata factory [repository]. Currently we have .INDEX(.vdb files), DDL, NATIVE (reading from source) support. >And can these different tools actually talk to each other to discover who/what tool is in charge of managing what metadata? Explain why do you think they need to discover and talk to each other? They each represent a metadata fragment in a VDB. The vdb.xml file is one defining them together as one artifact. >Does each tool have a window or view into the contents of the deployed artifact? They are not tools, it is just metadata, they themselves represent the views. When a user is writing a higher level metadata factory such as representing the view model, they need to know what else is available, so that they can make use of it in their transformations. That is where tools like Designer come in with nice GUI to make them design that. However, Teiid will still do validation at the deployment time, what they are referring to in their view transformations is in fact available and valid. > Add support exporting the Designer VDB as Dynamic VDB > ----------------------------------------------------- > > Key: TEIIDDES-2401 > URL: https://issues.jboss.org/browse/TEIIDDES-2401 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Reporter: Ramesh Reddy > > When a VDB is developed in the Designer, provide an option to export the given VDB as Dynamic VDB, which is simple XML format using DDL. > The server already provides mechanism to retrieve the schema (DDL) for a given model. Using this technique of retrieving the DDL, this feature can be built. > One caveat is support for XML document models in Dynamic VDB. When VDB contains XML document model, do not support this feature. > This has couple benefits > * Users can use these in Teiid for simplified usage. > * Can used to check the models into source repository like GIT or SVN etc and compare with later versions for modifications > * Open Shift > As for importing of Dynamic VDB, that can be handled as separate issue. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2408) Add remaining SQL/XML functions

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2408?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2408: ----------------------------------- Fix Version/s: 9.2 > Add remaining SQL/XML functions > ------------------------------- > > Key: TEIIDDES-2408 > URL: https://issues.jboss.org/browse/TEIIDDES-2408 > Project: Teiid Designer > Issue Type: Enhancement > Components: Teiid Integration > Reporter: Steven Hawkins > Fix For: 9.2 > > > Teiid added support for: > XMLTEXT - just a regular function > XMLEXISTS - a predicate with syntax similar to XMLQUERY > XMLCAST - similar to CAST > All are in the documentation and match the sql standard - https://docs.jboss.org/author/display/TEIID/XML+Functions -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2401) Add support exporting the Designer VDB as Dynamic VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2401?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2401: ---------------------------------------- * So if a user is using * file,database, a git repo or combination of all* for their artifact, are they using multiple tools to make this happen and what are they? * And can these different tools actually talk to each other to discover who/what tool is in charge of managing what metadata? * Does each tool have a window or view into the contents of the *deployed artifact*? > Add support exporting the Designer VDB as Dynamic VDB > ----------------------------------------------------- > > Key: TEIIDDES-2401 > URL: https://issues.jboss.org/browse/TEIIDDES-2401 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Reporter: Ramesh Reddy > > When a VDB is developed in the Designer, provide an option to export the given VDB as Dynamic VDB, which is simple XML format using DDL. > The server already provides mechanism to retrieve the schema (DDL) for a given model. Using this technique of retrieving the DDL, this feature can be built. > One caveat is support for XML document models in Dynamic VDB. When VDB contains XML document model, do not support this feature. > This has couple benefits > * Users can use these in Teiid for simplified usage. > * Can used to check the models into source repository like GIT or SVN etc and compare with later versions for modifications > * Open Shift > As for importing of Dynamic VDB, that can be handled as separate issue. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2408) Add remaining SQL/XML functions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2408?page=com.atlassian.jira.plu... ] Steven Hawkins reassigned TEIIDDES-2408: ---------------------------------------- Description: Teiid added support for: XMLTEXT - just a regular function XMLEXISTS - a predicate with syntax similar to XMLQUERY XMLCAST - similar to CAST All are in the documentation and match the sql standard - https://docs.jboss.org/author/display/TEIID/XML+Functions was:We should add the remaining functions, xmlparse, xmlserialize, xmlroot, etc. Assignee: (was: Steven Hawkins) Component/s: Teiid Integration > Add remaining SQL/XML functions > ------------------------------- > > Key: TEIIDDES-2408 > URL: https://issues.jboss.org/browse/TEIIDDES-2408 > Project: Teiid Designer > Issue Type: Enhancement > Components: Teiid Integration > Reporter: Steven Hawkins > > Teiid added support for: > XMLTEXT - just a regular function > XMLEXISTS - a predicate with syntax similar to XMLQUERY > XMLCAST - similar to CAST > All are in the documentation and match the sql standard - https://docs.jboss.org/author/display/TEIID/XML+Functions -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2408) Add remaining SQL/XML functions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2408?page=com.atlassian.jira.plu... ] Steven Hawkins moved TEIID-3252 to TEIIDDES-2408: ------------------------------------------------- Project: Teiid Designer (was: Teiid) Key: TEIIDDES-2408 (was: TEIID-3252) Affects Version/s: (was: 7.1) Component/s: (was: Query Engine) Fix Version/s: (was: 8.10) > Add remaining SQL/XML functions > ------------------------------- > > Key: TEIIDDES-2408 > URL: https://issues.jboss.org/browse/TEIIDDES-2408 > Project: Teiid Designer > Issue Type: Enhancement > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > We should add the remaining functions, xmlparse, xmlserialize, xmlroot, etc. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues December 2014