April 2012 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1327) Issues with "Create Relational View Model From Schema"

by Steven Hawkins (JIRA)

Steven Hawkins created TEIIDDES-1327: ---------------------------------------- Summary: Issues with "Create Relational View Model From Schema" Key: TEIIDDES-1327 URL: https://issues.jboss.org/browse/TEIIDDES-1327 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.6 Reporter: Steven Hawkins Right clicking on an .xsd and selecting "Create Relational View Model From Schema" presented a dialog where the select all option was not selectable by default. I had to first click on a global element and then hit select all. After running selecting all elements I got an error dialog with the detail "Create Virtual Tables from Global Entities Unexpected content type : org.eclipse.xsd.impl.XSDModelGroupImpl Unexpected content type : org.eclipse.xsd.impl.XSDModelGroupImpl" See the attached xsd. -- 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

12 years, 1 month

1
1
0 / 0

[JBoss JIRA] (TEIIDDES-1288) Enable the viewing of a query plan by importing from a file / clipboard

by Van Halbert (JIRA)

Van Halbert created TEIIDDES-1288: ------------------------------------- Summary: Enable the viewing of a query plan by importing from a file / clipboard Key: TEIIDDES-1288 URL: https://issues.jboss.org/browse/TEIIDDES-1288 Project: Teiid Designer Issue Type: Enhancement Components: Diagrams, Import/Export Reporter: Van Halbert It would be a good enhancement to the viewing of the query plan, if the person could import a query plan. Because the person who wants to view a query plan in designer, may not be the one who created it. I thought of that today when I wanted to view a plan someone attached to a jira. This plan was pretty big and hard to view just using a text editor. If I could have used designer to view the plan in a graphical manner, it would make the viewing easier. -- 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

12 years, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-427) Change the WSDL Generator to Embed Schemas in WSDLs Instead of Importing

by Ted Jones (JIRA)

Change the WSDL Generator to Embed Schemas in WSDLs Instead of Importing ------------------------------------------------------------------------ Key: TEIIDDES-427 URL: https://jira.jboss.org/jira/browse/TEIIDDES-427 Project: Teiid Designer Issue Type: Task Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.0 We need to embed schemas instead of importing them in our generated WSDL. This will eliminate resolution issues and make our WSDL more portable. Historically, customers have complained that the WSDL was hard to pass around since the schema import statements referred tot host and ports that were not available. at a minimum, we should add an option to the web services panel to embed or import the schema. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
9
0 / 0

[JBoss JIRA] Created: (TEIIDDES-632) Add WS-AtomicTransaction Support to Generated Web Service War

by Ted Jones (JIRA)

Add WS-AtomicTransaction Support to Generated Web Service War ------------------------------------------------------------- Key: TEIIDDES-632 URL: https://jira.jboss.org/browse/TEIIDDES-632 Project: Teiid Designer Issue Type: Feature Request Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.2 Need to add support for WS-AtomicTransaction in the generated web service war -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-603) Change Generated CXF WAR to create Dynamic Web Project

by Ted Jones (JIRA)

Change Generated CXF WAR to create Dynamic Web Project ------------------------------------------------------- Key: TEIIDDES-603 URL: https://jira.jboss.org/browse/TEIIDDES-603 Project: Teiid Designer Issue Type: Feature Request Components: VDB & Execution Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.2 When creating a CXF war from web service models, the war artifacts should be saved as a dynamic web projects in JBoss Tools. This will allow the user to view and manipulate the generated files and deploy to an AS server view -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
9
0 / 0

[JBoss JIRA] Created: (TEIIDDES-983) Add Export Option for Generated SOAP and REST Wars

by Ted Jones (JIRA)

Add Export Option for Generated SOAP and REST Wars -------------------------------------------------- Key: TEIIDDES-983 URL: https://issues.jboss.org/browse/TEIIDDES-983 Project: Teiid Designer Issue Type: Enhancement Components: Import/Export Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.5 Currently (in 7.4), the JBossWS-CXF and RESTEasy wars are generated via the VDB context menu option Modeling->Generate JBossWS-CXF WAR or Generate RESTEasy WAR. It would be nice to make this an Export option to flow more logically with the rest of Designer processing. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
3
0 / 0

[JBoss JIRA] (TEIIDDES-319) Request for single table import option in Web Service As Relational web service

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-319?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-319. ----------------------------------- Resolution: Duplicate Issue This was completed in 7.7 Teiid Designer release as part of the WSDL to Relational Source & View models importer. Basically REQUEST & RESPONSE procedures are created and then used in a Wrapper procedure containing the input parameters AND the output result se. > Request for single table import option in Web Service As Relational web service > ------------------------------------------------------------------------------- > > Key: TEIIDDES-319 > URL: https://issues.jboss.org/browse/TEIIDDES-319 > Project: Teiid Designer > Issue Type: Feature Request > Affects Versions: Future > Environment: 5.5.3 GA on Linux > Reporter: Greg Haber > Assignee: Barry LaFond > Fix For: 7.7.1 > > > This is a longer term feature request - not expecting any near term resolution. > It would be great if the web service as relational importer could have an option to model a web service with a single table representing both the request and response, instead of as separate tables as today. Not sure if it makes sense to allow this for heirarchical response web services, or only simple ones returning a flat schema. > Whenever possible I always manually model web service connections this way because of the pros - but would be much better if the importer would do it for me. > Pros: > -Would avoid multiple queries to web service connector for a single web service call (since XML-Relational connectors don't support join pushdown) - simpler query plans > -With that single call it lessens use/paves way for disabling the XML-Relational connector internal doc cache (which, at least in 5.0SP2, was a _big_ bottleneck in the field with concurrent calls to the same web service, if the web service takes more than a few seconds to respond - I believe because the whole doc cache is locked on both read and write, effectively resulting in single threaded and blocking behavior. Anyway, just speculating on the cause, but it is established that in 5.0SP2 that single-table web services were much faster than multi-table ones). > -Would work in preview > Cons: > -Does not logically represent the way web services actually work > -Confusing as it jumbles together elements from two XML docs in a single relational base table -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-291) XML-Relational and WSDL-Relational importers do not understand the substitutionGroup attribute of xsd:Element

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-291?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-291: ---------------------------------- Fix Version/s: 8.0 (was: 7.7.1) > XML-Relational and WSDL-Relational importers do not understand the substitutionGroup attribute of xsd:Element > ------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-291 > URL: https://issues.jboss.org/browse/TEIIDDES-291 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Reporter: John Doyle > Priority: Minor > Fix For: 8.0 > > Attachments: XSDTest7.java > > > See the issue tracker: > https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&ti... > Take a look at section 2.2.2.2 of the XSD spec. > http://www.w3.org/TR/xmlschema-1/ > Or this nice example: > http://www.w3schools.com/Schema/schema_complex_subst.asp > As I read the spec, these substitution groups have no effect on the structure of the XML defined by the XSD, only the names that allowed for a particular element in the XML. > We don't support this in the importer now. We would have to add functionality to find the substitution groups and add additional XPaths so that the connector could either /name or /navn in the xml document. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-119) XML-Relaional modeling needs to be easier for sources that do not provide an XSD.

by John Doyle (JIRA)

XML-Relaional modeling needs to be easier for sources that do not provide an XSD. --------------------------------------------------------------------------------- Key: TEIIDDES-119 URL: https://jira.jboss.org/jira/browse/TEIIDDES-119 Project: Teiid Designer Issue Type: Feature Request Components: Modeling Reporter: John Doyle Assignee: John Doyle The main case for this is REST services. REST services do not have a standard description mechanism like WSDL for SOAP services. The inputs and outputs of the service might be documented in a HTML help page, with sample XML documents, with WADL, etc. Hand modeling is too difficult, so we need to come up with other assists. The solution is probably a mix of new features and documented best practices. For example: Add WADL support to the importer. Document use of a schema from XML tool (like inst2XSD) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
11
0 / 0

[JBoss JIRA] (TEIIDDES-1111) Create a model(s) (view/source) based on the schema and type of data source provided

by Ramesh Reddy (Created) (JIRA)

Create a model(s) (view/source) based on the schema and type of data source provided ------------------------------------------------------------------------------------ Key: TEIIDDES-1111 URL: https://issues.jboss.org/browse/TEIIDDES-1111 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Reporter: Ramesh Reddy There have been many requests from users in the recent past to auto-generate source and view models that can consume the XML coming in the specified in a schema file. The current XML document model, take in a XSD and maps the relational data into XML data. This request is exact opposite of it in the consuming side. The data is coming in as XML, need to expose them as relational. I strongly believe that this needs to be done as part of TEIIDDES-1078, not create separate importers to minimize the user experience with modelling any XML data. The data sources can File, SOAP service or Rest service currently, but may not be restricted to those. -- 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

12 years, 1 month

4
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues April 2012