May 2012 - teiid-designer-issues - Jboss List Archives

[JBoss JIRA] (TEIIDDES-1272) Add Support for Attributes in the XML File Importer

by Ted Jones (JIRA)

Ted Jones created TEIIDDES-1272: ----------------------------------- Summary: Add Support for Attributes in the XML File Importer Key: TEIIDDES-1272 URL: https://issues.jboss.org/browse/TEIIDDES-1272 Project: Teiid Designer Issue Type: Enhancement Components: Import/Export Affects Versions: 7.6 Reporter: Ted Jones Fix For: 7.7.1 Need to support modeling attributes when importing XML files -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
3
0 / 0

[JBoss JIRA] (TEIIDDES-1242) Designer needs to upgrade to Teiid 7.7.x client to fix TEIID-1882

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1242?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1242: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> made a private comment on [bug 781176|https://bugzilla.redhat.com/show_bug.cgi?id=781176] > Designer needs to upgrade to Teiid 7.7.x client to fix TEIID-1882 > ----------------------------------------------------------------- > > Key: TEIIDDES-1242 > URL: https://issues.jboss.org/browse/TEIIDDES-1242 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 7.6 > Reporter: Steven Hawkins > Assignee: Barry LaFond > Priority: Critical > Fix For: 7.7 > > > The Handshake and LogonResult classes are not properly accounting for backwards compatibility. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1233) Teiid cannot handle child elements belonging to a different namespace

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1233?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-1233: ------------------------------------------ Ted/Barry, At least what I inferred initially was that this is an XML document model scenario, see the attached vdb. If the user hand models the document, then the namespace settings are not correctly conveyed in the index via the MappingDocumentFormatter expects an associated schema. It would be best though if Debbie could confirm this assumption as the original case was not entirely clear. > Teiid cannot handle child elements belonging to a different namespace > --------------------------------------------------------------------- > > Key: TEIIDDES-1233 > URL: https://issues.jboss.org/browse/TEIIDDES-1233 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.6 > Reporter: Debbie Steigner > Assignee: Ted Jones > Fix For: 7.7.1 > > Attachments: foo.zip > > > In the case where a web service is returning a response similar to the > following: > <ns1:searchMidbWSResponse ... > > < ns1:return> > < ns1:Site> > <ns2:PropOne>...</ ns2:PropOne> > < ns2:PropTwo>...</ ns2:PropTwo> > etc... > </ ns1:Site> > </ ns1:return> > </ ns1:searchMidbWSResponse> > Notice that all of the Site property elements belong to a different namespace > (alias=ns2) whereas the outer elements belong to the namespace with the ns1 > alias. It looks like EDS cannot handle child elements belonging to a different > namespace. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1233) Teiid cannot handle child elements belonging to a different namespace

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1233?page=com.atlassian.jira.plu... ] Ted Jones edited comment on TEIIDDES-1233 at 5/8/12 10:36 PM: -------------------------------------------------------------- We can definitely handle this using the WSDL to Source importer, however Steve is talking about document models which is a different animal, so I'm not sure what the actual use case is here. Are we generating web service models and not handling the response correctly, or is this using SQL/XML? Debbie, do you have that information? was (Author: tejones): We can definitely handle this using the WSDL to Source importer, however Steve is talking about document models which is a different animal. so I'm not sure what the actual use case is here. Are we generating web service models and not handling the response correctly, or is this using SQL/XML? Debbie, do you have that information? > Teiid cannot handle child elements belonging to a different namespace > --------------------------------------------------------------------- > > Key: TEIIDDES-1233 > URL: https://issues.jboss.org/browse/TEIIDDES-1233 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.6 > Reporter: Debbie Steigner > Assignee: Ted Jones > Fix For: 7.7.1 > > Attachments: foo.zip > > > In the case where a web service is returning a response similar to the > following: > <ns1:searchMidbWSResponse ... > > < ns1:return> > < ns1:Site> > <ns2:PropOne>...</ ns2:PropOne> > < ns2:PropTwo>...</ ns2:PropTwo> > etc... > </ ns1:Site> > </ ns1:return> > </ ns1:searchMidbWSResponse> > Notice that all of the Site property elements belong to a different namespace > (alias=ns2) whereas the outer elements belong to the namespace with the ns1 > alias. It looks like EDS cannot handle child elements belonging to a different > namespace. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1233) Teiid cannot handle child elements belonging to a different namespace

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1233?page=com.atlassian.jira.plu... ] Ted Jones commented on TEIIDDES-1233: ------------------------------------- We can definitely handle this using the WSDL to Source importer, however Steve is talking about document models which is a different animal. so I'm not sure what the actual use case is here. Are we generating web service models and not handling the response correctly, or is this using SQL/XML? Debbie, do you have that information? > Teiid cannot handle child elements belonging to a different namespace > --------------------------------------------------------------------- > > Key: TEIIDDES-1233 > URL: https://issues.jboss.org/browse/TEIIDDES-1233 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.6 > Reporter: Debbie Steigner > Assignee: Ted Jones > Fix For: 7.7.1 > > Attachments: foo.zip > > > In the case where a web service is returning a response similar to the > following: > <ns1:searchMidbWSResponse ... > > < ns1:return> > < ns1:Site> > <ns2:PropOne>...</ ns2:PropOne> > < ns2:PropTwo>...</ ns2:PropTwo> > etc... > </ ns1:Site> > </ ns1:return> > </ ns1:searchMidbWSResponse> > Notice that all of the Site property elements belong to a different namespace > (alias=ns2) whereas the outer elements belong to the namespace with the ns1 > alias. It looks like EDS cannot handle child elements belonging to a different > namespace. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1339) Add Table Gerneration to WSDL to Relational Importer

by Ted Jones (JIRA)

Ted Jones created TEIIDDES-1339: ----------------------------------- Summary: Add Table Gerneration to WSDL to Relational Importer Key: TEIIDDES-1339 URL: https://issues.jboss.org/browse/TEIIDDES-1339 Project: Teiid Designer Issue Type: Enhancement Components: Import/Export Affects Versions: 7.7 Reporter: Ted Jones Fix For: 7.7.1 Using the generated wrapper procedure, we can/should also generate a virtual table. We should allow the user to define an optional access pattern. It may be possible to integrate the table generation with the new virtual table wizard should be explored as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

2
4
0 / 0

[JBoss JIRA] (TEIIDDES-1362) Action Set for Import XML via URL Should Check for XML vs REST

by Ted Jones (JIRA)

Ted Jones created TEIIDDES-1362: ----------------------------------- Summary: Action Set for Import XML via URL Should Check for XML vs REST Key: TEIIDDES-1362 URL: https://issues.jboss.org/browse/TEIIDDES-1362 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.1.1 Reporter: Ted Jones Fix For: 7.7.1 Using the action set to import a URL based XML file (create CP) , I am not allowed to check REST vs XML. We should add the dialog to select one or the other prior to showing the CP dialog. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

2
2
0 / 0

[JBoss JIRA] (TEIIDDES-280) Update Count metadata property is not avaialble on the Web Service procedure

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-280?page=com.atlassian.jira.plug... ] Barry LaFond commented on TEIIDDES-280: --------------------------------------- A) XML Service model is retired so only fix here is to add the "Update Count" property to Web Service Operations B) Mechanism to extend the Web Services model is via the new MED (Model Extension Definition) framework So we'll need to: 1) Create a built-in MED maybe called "Web Services Built-in" - Add ONE extended property on an Operation with display name "Update Count" - ALLOWABLE VALUES : AUTO, MULTIPLE, ONE, ZERO 2) Have to wire this MED up so it's applied any time a Web Services model is created 3) Maybe create a Validation "warning" stating that "Web Services Model does not reflect built-in extended properties. Select WS Model and choose Modeling > Manage Model Extension Definitions to apply built-in extensions" See Dan Florian for details. We already have built-in MEDs for Salesforce and basic "relational" model properties, so there are some examples to work from. > Update Count metadata property is not avaialble on the Web Service procedure > ---------------------------------------------------------------------------- > > Key: TEIIDDES-280 > URL: https://issues.jboss.org/browse/TEIIDDES-280 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Reporter: Ramesh Reddy > Assignee: Paul Richardson > Fix For: 7.7.1 > > > "Update Count" metadata is not available on the Web Service procedure, this is only available on the virtual procedures. This data is used at run time to determine if procedure is "readonly", or does "single" or "multiple" updates to the underlaying databases. If this property not available then by default it is assumed that "multiple" updates and subject to the transactional restrictions in the server and dqp. > Per SteveH, this property must be on any kind of procedure, may that be virtual, web and xml service. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-280) Update Count metadata property is not avaialble on the Web Service procedure

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-280?page=com.atlassian.jira.plug... ] Paul Richardson reassigned TEIIDDES-280: ---------------------------------------- Assignee: Paul Richardson > Update Count metadata property is not avaialble on the Web Service procedure > ---------------------------------------------------------------------------- > > Key: TEIIDDES-280 > URL: https://issues.jboss.org/browse/TEIIDDES-280 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Reporter: Ramesh Reddy > Assignee: Paul Richardson > Fix For: 7.7.1 > > > "Update Count" metadata is not available on the Web Service procedure, this is only available on the virtual procedures. This data is used at run time to determine if procedure is "readonly", or does "single" or "multiple" updates to the underlaying databases. If this property not available then by default it is assumed that "multiple" updates and subject to the transactional restrictions in the server and dqp. > Per SteveH, this property must be on any kind of procedure, may that be virtual, web and xml service. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1360) CLONE - XML Data File Import options: Have an xquery, but am told it's empty or null

by Paul Nittel (JIRA)

Paul Nittel created TEIIDDES-1360: ------------------------------------- Summary: CLONE - XML Data File Import options: Have an xquery, but am told it's empty or null Key: TEIIDDES-1360 URL: https://issues.jboss.org/browse/TEIIDDES-1360 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.7.1 Environment: JBDS 5.0 Beta 3 with SOA-tooling Beta 1 Reporter: Paul Nittel Assignee: Barry LaFond Fix For: 7.7.1 When I get to this step in the XML Data File import wizard (executed via the Consume Web Service action set, step generate relational models from WSDL), and I select a couple of attributes to be transformed into relational columns, I cannot proceed due to the wizard's claim that my xQuery is empty or null. The source XML file is attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues May 2012