August 2011 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-1050) NPE in SOAPConnectionInfoProvider when NameInSource is null

by Ted Jones (JIRA)

NPE in SOAPConnectionInfoProvider when NameInSource is null ----------------------------------------------------------- Key: TEIIDDES-1050 URL: https://issues.jboss.org/browse/TEIIDDES-1050 Project: Teiid Designer Issue Type: Bug Components: Web Services Support Affects Versions: 7.5 Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.4.2, 7.6 The following exception is thrown when creating/setting a connection profile (SOAP Web Service) and the NameInSource is not set: -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-982) Web Services Connection Profile dialog doesn't provide guidance when CP has no valid Teiid connection properties

by Paul Nittel (JIRA)

Web Services Connection Profile dialog doesn't provide guidance when CP has no valid Teiid connection properties ---------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-982 URL: https://issues.jboss.org/browse/TEIIDDES-982 Project: Teiid Designer Issue Type: Bug Components: Web Services Support Affects Versions: 7.4 Environment: JBDS 4.1.0 CR1 Reporter: Paul Nittel I'm trying to replicate the Weather example using Designer. I created (generated?) the invoke procedure and modeled a view whose transformation SQL contains the XML parsing constructs used in the example. I created a connection profile as part of defining the data source. This process involves the Web Services Data Source dialog (see screenshot). For this I entered the URL as the SOAP endpoint. Al other field were left blank. Test connection returned a success message, yet when I exited the dialog, the resulting profile was in error "There are no valid Teiid connection properties associated with this connection profile". (See the other screenshot.) Perhaps this is evidence of an underlying bug, but it represents a usability issue since it doesn't clearly explain what's missing or incorrect. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
10
0 / 0

[JBoss JIRA] Created: (TEIIDDES-885) Preview Data fails if attempted immediately after "Save" model.

by Barry LaFond (JIRA)

Preview Data fails if attempted immediately after "Save" model. --------------------------------------------------------------- Key: TEIIDDES-885 URL: https://issues.jboss.org/browse/TEIIDDES-885 Project: Teiid Designer Issue Type: Bug Components: Data Preview Affects Versions: 7.3 Reporter: Barry LaFond Assignee: Dan Florian Priority: Critical Fix For: 7.4 Set up Designer with sample project with source model and connect to Teiid Instance 1) Open Package diagram for model and select Table 2) Select Preview Data action and see successful results 3) Drag diagram component and Save 4) Click Preview Data action right after click save 5) Get query result of: "Remote org.teiid.core.TeiidProcessingException: Failed to find the Connection Factory with JNDI name PREVIEW_42463872-ecd7-46dd-93b1-450354a53b55_PartsProject_PartsSourceB. Please check the name or deploy the Connection Factory with specified name." 6) Wait a few more seconds and try Preview Data again and it'll be successful Guessing the create/deploy/redeploy VDB and maybe Data Source jobs aren't complete yet or are waiting for auto-build to run or something. Maybe in the Preview Data action we can check the PreviewManager and stop the action of PVDB jobs are running. Or we schedule/wait the new PVDB jobs until existing are finished running. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1056) RuntimeAdapter Needs To Strip Off Extension Property Namespace Prefix Before Indexing

by Dan Florian (JIRA)

RuntimeAdapter Needs To Strip Off Extension Property Namespace Prefix Before Indexing ------------------------------------------------------------------------------------- Key: TEIIDDES-1056 URL: https://issues.jboss.org/browse/TEIIDDES-1056 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.5 Reporter: Dan Florian Assignee: Dan Florian Fix For: 7.5 The Runtime Adapter is passing the extension property full identifier as the property identifier. The full identifier includes the model extension definition namespace prefix, a delimiter, and the property ID. It should be passing the extension property's simple ID which strips off the namespace prefix and the delimiter. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1052) Error Log Message After Removing REST Extension Properties From 7.4 Model

by Dan Florian (JIRA)

Error Log Message After Removing REST Extension Properties From 7.4 Model ------------------------------------------------------------------------- Key: TEIIDDES-1052 URL: https://issues.jboss.org/browse/TEIIDDES-1052 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.4 Reporter: Dan Florian Assignee: Dan Florian Fix For: 7.5 Attachments: RestBooksToo.xmi This message is displayed in the Eclipse error log after removing the REST model extension definition (MED) from a 7.4 REST-enabled model: Value " " is not an allowed value for property "ext-custom:REST-METHOD." Value was reset to be an empty value. The message is being logged from ModelExtensionPropertyDescriptor (line 249). It is only a log message and doesn't really affect anything but should be fixed. The properties are successfully removed from the model. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
3
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-1054) RFE in Teiid Designer for an Unselect all button when updating Source Models

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1054?page=com.atlassian.jira.plu... ] Van Halbert moved SOA-3339 to TEIIDDES-1054: -------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise SOA Platform) Key: TEIIDDES-1054 (was: SOA-3339) Affects Version/s: 7.1.1 (was: 5.1.0 GA) Component/s: Modeling (was: EDS) Security: (was: Public) > RFE in Teiid Designer for an Unselect all button when updating Source Models > ---------------------------------------------------------------------------- > > Key: TEIIDDES-1054 > URL: https://issues.jboss.org/browse/TEIIDDES-1054 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Affects Versions: 7.1.1 > Reporter: Debbie Steigner > > When updating a source model, on the dialog which shows you the differences between the original and updated model (new/old/unchanged). > By default all the items are checked, meaning the source model will be updated to only what has been selected in the previous screen. > Most of the time we want to *add* tables to our source model. This means we need to unselect every item in the differences dialog except the ones we just selected. > There's no deselect all button, which we would like, so we don't have to deselect every checkbox one by one (especially when we have hundreds of tables in a model). > These checkbox items are the children of a checkbox for the schema, so typically in a UI like this you would expect unselecting the parent checkbox to unselect all its children also. This doesn't happen. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1051) Importing Salesforce tables into an empty relational model does not apply extension properties to new tables

by Barry LaFond (JIRA)

Importing Salesforce tables into an empty relational model does not apply extension properties to new tables ------------------------------------------------------------------------------------------------------------ Key: TEIIDDES-1051 URL: https://issues.jboss.org/browse/TEIIDDES-1051 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.5 Reporter: Barry LaFond Assignee: Dan Florian Priority: Blocker Fix For: 7.5 Import SF tables into empty existing relational model and the extension properties don't get set in the model on the tables. If I import and create a NEW relational model in the process, the extension properties DO get set properly -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1046) Enabling REST for Procedures the Were RESTful in 7.4.2 Leaves the Legacy Tags

by Ted Jones (JIRA)

Enabling REST for Procedures the Were RESTful in 7.4.2 Leaves the Legacy Tags ----------------------------------------------------------------------------- Key: TEIIDDES-1046 URL: https://issues.jboss.org/browse/TEIIDDES-1046 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.5 Reporter: Ted Jones Assignee: Dan Florian Fix For: 7.5 I have a model from 7.4.2 that exposed procedures RESTfully (they had annoation tags for REST-METHOD and URI). Opening the model in 7.5, the "Enable REST for Procedures" option was lit. It should have said "Disable REST for Procedures". After enabling REST (and saving) the new properties were added and the old properties were still in the model file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1040) Removing MED From Model Causes NPE

by Ted Jones (JIRA)

Removing MED From Model Causes NPE ---------------------------------- Key: TEIIDDES-1040 URL: https://issues.jboss.org/browse/TEIIDDES-1040 Project: Teiid Designer Issue Type: Bug Reporter: Ted Jones Removing the REST MED from a model causes the following exception: Exception in thread "ModelBuffer.Save" java.lang.NullPointerException at org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getURIFragment(XMLHelperImpl.java:719) at org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getIDREF(XMLHelperImpl.java:753) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveIDRefSingle(XMLSaveImpl.java:1972) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiSaveImpl.saveIDRefSingle(MtkXmiSaveImpl.java:298) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1318) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiSaveImpl.saveElementID(MtkXmiSaveImpl.java:248) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1174) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1035) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveContainedMany(XMLSaveImpl.java:2386) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1533) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiSaveImpl.saveElementID(MtkXmiSaveImpl.java:248) at org.eclipse.emf.ecore.xmi.impl.XMISaveImpl.writeTopObjects(XMISaveImpl.java:90) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.traverse(XMLSaveImpl.java:592) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.save(XMLSaveImpl.java:256) at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doSave(XMLResourceImpl.java:206) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiResourceImpl.doSave(MtkXmiResourceImpl.java:354) at org.eclipse.emf.ecore.resource.impl.ResourceImpl.save(ResourceImpl.java:1406) at com.metamatrix.modeler.internal.core.workspace.ModelBufferImpl.saveInTransaction(ModelBufferImpl.java:559) at com.metamatrix.modeler.internal.core.workspace.ModelBufferImpl$1.run(ModelBufferImpl.java:488) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1049) When A Model Extension Definition (MED) Is Removed From A Model All The Associated EObject Properties Are Not Being Removed

by Dan Florian (JIRA)

When A Model Extension Definition (MED) Is Removed From A Model All The Associated EObject Properties Are Not Being Removed --------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-1049 URL: https://issues.jboss.org/browse/TEIIDDES-1049 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.4 Reporter: Dan Florian Assignee: Dan Florian Fix For: 7.5 When removing a MED from a model the MED gets removed but only the associated properties of the selected Procedure are also removed. There could be other Procedures that also have those MED properties and those need to be removed also. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues August 2011