February 2012 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1258) Confusing message when modeling a String data type that doesn't have the length specified

by Van Halbert (JIRA)

Van Halbert created TEIIDDES-1258: ------------------------------------- Summary: Confusing message when modeling a String data type that doesn't have the length specified Key: TEIIDDES-1258 URL: https://issues.jboss.org/browse/TEIIDDES-1258 Project: Teiid Designer Issue Type: Bug Components: Modeling Reporter: Van Halbert When modeling a column defined as a String, but no length has been set, you get the warning message: "Missing or invalid Length on column with a string/character datatype (See validation Preferences)" This is confusing for several reasons: - If its a warning, then the value must not be invalid - It would be good to indicate what the default length will be when the length isn't set -- 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

6
7
0 / 0

[JBoss JIRA] (TEIIDDES-1167) Validation error after entering Overview info and saving MED

by Barry LaFond (Created) (JIRA)

Validation error after entering Overview info and saving MED ------------------------------------------------------------ Key: TEIIDDES-1167 URL: https://issues.jboss.org/browse/TEIIDDES-1167 Project: Teiid Designer Issue Type: Bug Components: Editors Affects Versions: 7.6 Reporter: Barry LaFond Priority: Minor Problem marker stated: cvc-complex-type.2.4.b: The content of element 'modelExtension' is not complete. One of '{"http://org.teiid.modelExtension/2011":extendedMetaclass}' is expected. RelationalAppearance.mxd /MyMeds Unknown Model Extension Definition Problem Error went away once I created Property definition for a model object and "saved" the MED. -- 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

2
2
0 / 0

[JBoss JIRA] (TEIIDDES-1171) When removing Model Object in MED editor, the "Remove Model Object" dialog has the full metamodel class name.

by Barry LaFond (Created) (JIRA)

When removing Model Object in MED editor, the "Remove Model Object" dialog has the full metamodel class name. --------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-1171 URL: https://issues.jboss.org/browse/TEIIDDES-1171 Project: Teiid Designer Issue Type: Bug Components: Editors Affects Versions: 7.6 Reporter: Barry LaFond Priority: Minor When removing Model Object in MED editor, the "Remove Model Object" dialog has the full metamodel class name. - I removed a "View" model object and the dialog refered to a "com.metamatrix.metamodels.relational.impl.ViewImpl" object. -- 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

2
2
0 / 0

[JBoss JIRA] (TEIIDDES-1234) Generate WAR action processes with workspace models instead of model entries in the selected VDB

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1234: -------------------------------------- Summary: Generate WAR action processes with workspace models instead of model entries in the selected VDB Key: TEIIDDES-1234 URL: https://issues.jboss.org/browse/TEIIDDES-1234 Project: Teiid Designer Issue Type: Bug Components: Web Services Support Affects Versions: 7.7 Reporter: Barry LaFond Assignee: Ted Jones Priority: Critical Fix For: 7.7 GenerateWarAction.selectionChanged() appears to be mixing apples and oranges. (See below) I think the intent was to get the VdbModelEntry objects and cache up a list of WS Models for later use generating the proper procedure calls/URLs?? The colde below, however, is finding the corresponding ModelResource in the workspace for each entry, which could easily be "out of sync". Users would be unaware that the WAR they are creating might not be what they expect. wsModelResources = new ArrayList<ModelResource>(); for (VdbModelEntry vdbModelEntry : modelEntrySet) { final ModelResource modelResource = ModelerCore.getModelWorkspace().findModelResource(vdbModelEntry.getName()); if (ModelIdentifier.isWebServicesViewModel(modelResource)) { enable = true; // Add to our ArrayList of ModelResources. These // will be used to generate the war artifacts. wsModelResources.add(modelResource); } } So I think we either not allow users to perform this action if the VDB was "out of sync" (probably not the best option) or Find another way to pass the model info necessary for the generator to perform whats needed. Note that in VdbEditor class there is an example of creating a "Temporary" EMF model container in order to interrogate the models. So I believe it should be possible. -- 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

2
3
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

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

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

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

2
3
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

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

4
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues February 2012