June 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2552) REST connection profile wizard creates URL with parameters in wrong order

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2552?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2552: ---------------------------------------- The "URI" parameter should be called "PATH" parameters to be sync with how everyone calls them > REST connection profile wizard creates URL with parameters in wrong order > ------------------------------------------------------------------------- > > Key: TEIIDDES-2552 > URL: https://issues.jboss.org/browse/TEIIDDES-2552 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 9.0.2 Beta2 > Reporter: Andrej Šmigala > Priority: Critical > Attachments: Newconnectionprofile_001.png > > > When defining parameters for REST connection profile, they are added to the URL in the order they are defined. This results in wrong URL in case a Query parameter is defined before a URI parameter. > The URI parameters should always be added to the URL before the Query parameters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2552) REST connection profile wizard creates URL with parameters in wrong order

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2552?page=com.atlassian.jira.plu... ] Ramesh Reddy updated TEIIDDES-2552: ----------------------------------- Priority: Critical (was: Major) > REST connection profile wizard creates URL with parameters in wrong order > ------------------------------------------------------------------------- > > Key: TEIIDDES-2552 > URL: https://issues.jboss.org/browse/TEIIDDES-2552 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 9.0.2 Beta2 > Reporter: Andrej Šmigala > Priority: Critical > Attachments: Newconnectionprofile_001.png > > > When defining parameters for REST connection profile, they are added to the URL in the order they are defined. This results in wrong URL in case a Query parameter is defined before a URI parameter. > The URI parameters should always be added to the URL before the Query parameters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2553) Changing parameter types in REST connection results in wrong URL

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2553?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-2553: ---------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1228567 > Changing parameter types in REST connection results in wrong URL > ---------------------------------------------------------------- > > Key: TEIIDDES-2553 > URL: https://issues.jboss.org/browse/TEIIDDES-2553 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 9.0.2 Beta2 > Reporter: Andrej Šmigala > > Changing the type of a parameter in the REST connection profile causes the generated URL to be wrong. Also, the Preview URL is not updated after changing the type, only after some other action (testing connection, changing the default value etc). > Furthermore, removing the paramters does not work if the type of the parameter has been changed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2553) Changing parameter types in REST connection results in wrong URL

by Andrej Šmigala (JIRA)

Andrej Šmigala created TEIIDDES-2553: ---------------------------------------- Summary: Changing parameter types in REST connection results in wrong URL Key: TEIIDDES-2553 URL: https://issues.jboss.org/browse/TEIIDDES-2553 Project: Teiid Designer Issue Type: Bug Components: Web Services Support Affects Versions: 9.0.2 Beta2 Reporter: Andrej Šmigala Changing the type of a parameter in the REST connection profile causes the generated URL to be wrong. Also, the Preview URL is not updated after changing the type, only after some other action (testing connection, changing the default value etc). Furthermore, removing the paramters does not work if the type of the parameter has been changed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2552) REST connection profile wizard creates URL with parameters in wrong order

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2552?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-2552: ---------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1228557 > REST connection profile wizard creates URL with parameters in wrong order > ------------------------------------------------------------------------- > > Key: TEIIDDES-2552 > URL: https://issues.jboss.org/browse/TEIIDDES-2552 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 9.0.2 Beta2 > Reporter: Andrej Šmigala > Attachments: Newconnectionprofile_001.png > > > When defining parameters for REST connection profile, they are added to the URL in the order they are defined. This results in wrong URL in case a Query parameter is defined before a URI parameter. > The URI parameters should always be added to the URL before the Query parameters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2552) REST connection profile wizard creates URL with parameters in wrong order

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2552?page=com.atlassian.jira.plu... ] Andrej Šmigala updated TEIIDDES-2552: ------------------------------------- Attachment: Newconnectionprofile_001.png > REST connection profile wizard creates URL with parameters in wrong order > ------------------------------------------------------------------------- > > Key: TEIIDDES-2552 > URL: https://issues.jboss.org/browse/TEIIDDES-2552 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 9.0.2 Beta2 > Reporter: Andrej Šmigala > Attachments: Newconnectionprofile_001.png > > > When defining parameters for REST connection profile, they are added to the URL in the order they are defined. This results in wrong URL in case a Query parameter is defined before a URI parameter. > The URI parameters should always be added to the URL before the Query parameters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2552) REST connection profile wizard creates URL with parameters in wrong order

by Andrej Šmigala (JIRA)

Andrej Šmigala created TEIIDDES-2552: ---------------------------------------- Summary: REST connection profile wizard creates URL with parameters in wrong order Key: TEIIDDES-2552 URL: https://issues.jboss.org/browse/TEIIDDES-2552 Project: Teiid Designer Issue Type: Bug Components: Web Services Support Affects Versions: 9.0.2 Beta2 Reporter: Andrej Šmigala When defining parameters for REST connection profile, they are added to the URL in the order they are defined. This results in wrong URL in case a Query parameter is defined before a URI parameter. The URI parameters should always be added to the URL before the Query parameters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2549) Designer considers the current Teiid version as unsupported

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2549?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2549: ----------------------------------- Fix Version/s: 9.1 9.0.2 Beta2 (was: 9.2) (was: 9.0.3) > Designer considers the current Teiid version as unsupported > ----------------------------------------------------------- > > Key: TEIIDDES-2549 > URL: https://issues.jboss.org/browse/TEIIDDES-2549 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.2 Beta2 > Reporter: Andrej Šmigala > Assignee: Paul Richardson > Priority: Critical > Fix For: 9.1, 9.0.2 Beta2, 9.0.2 > > Attachments: msg1.png, msg2.png > > > Selecting Teiid 8.7.1 as the default server results in *two* messages about unsupported server version, even though it is supported. This is very confusing for the user. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2549) Designer considers the current Teiid version as unsupported

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2549?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2549: ----------------------------------- Fix Version/s: 9.0.2 > Designer considers the current Teiid version as unsupported > ----------------------------------------------------------- > > Key: TEIIDDES-2549 > URL: https://issues.jboss.org/browse/TEIIDDES-2549 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.2 Beta2 > Reporter: Andrej Šmigala > Assignee: Paul Richardson > Priority: Critical > Fix For: 9.1, 9.0.2 Beta2, 9.0.2 > > Attachments: msg1.png, msg2.png > > > Selecting Teiid 8.7.1 as the default server results in *two* messages about unsupported server version, even though it is supported. This is very confusing for the user. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2551) Renaming source model in a project exported from older version of designer breaks dependent models

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2551?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2551: ----------------------------------- Fix Version/s: 9.1 9.0.2 Beta2 9.0.2 > Renaming source model in a project exported from older version of designer breaks dependent models > -------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2551 > URL: https://issues.jboss.org/browse/TEIIDDES-2551 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 9.0.2 Beta2 > Environment: Windows 7 > Reporter: Andrej Šmigala > Priority: Blocker > Fix For: 9.1, 9.0.2 Beta2, 9.0.2 > > Attachments: ModelRefactoringProject.zip > > > When trying to rename a source model in a model that was exported from older version of designer, the refactoring fails and the dependent view models are completely broken. This does not happen when the same models are created from scratch. > Only happens on Windows. > Stacktrace: > {noformat} > org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$1DiagnosticWrappedException: org.xml.sax.SAXParseExceptionpublicId: file:/C:/Users/dv/workspaces/jbds-8.1.0.GA_jbdsis-8.0.2.CR1/ModelRefactoringProject/partssupplier_view_3.xmi; systemId: file:/C:/Users/dv/workspaces/jbds-8.1.0.GA_jbdsis-8.0.2.CR1/ModelRefactoringProject/partssupplier_view_3.xmi; lineNumber: 6; columnNumber: 112; Element type "modelImports" must be followed by either attribute specifications, ">" or "/>". > at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.handleDemandLoadException(ResourceSetImpl.java:319) > at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoadHelper(ResourceSetImpl.java:278) > at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getResource(ResourceSetImpl.java:406) > at org.teiid.designer.core.resource.EmfResourceSetImpl.getResource(EmfResourceSetImpl.java:235) > at org.teiid.designer.core.container.ContainerImpl.getResource(ContainerImpl.java:819) > at org.teiid.designer.core.container.ContainerImpl.getOrCreateResource(ContainerImpl.java:204) > at org.teiid.designer.core.workspace.ModelBufferImpl.open(ModelBufferImpl.java:237) > at org.teiid.designer.core.workspace.ModelResourceImpl.openBuffer(ModelResourceImpl.java:445) > at org.teiid.designer.core.workspace.OpenableImpl.getBuffer(OpenableImpl.java:405) > at org.teiid.designer.core.workspace.OpenableImpl.getBufferHack(OpenableImpl.java:378) > at org.teiid.designer.core.workspace.ModelResourceImpl.getModelAnnotation(ModelResourceImpl.java:634) > at org.teiid.designer.core.extension.ModelExtensionUtils.getResourceAnnotationImpl(ModelExtensionUtils.java:422) > at org.teiid.designer.core.extension.ModelExtensionUtils.getResourceAnnotation(ModelExtensionUtils.java:474) > at org.teiid.designer.core.extension.ModelExtensionUtils.getSupportedNamespaces(ModelExtensionUtils.java:503) > at org.teiid.designer.core.extension.ModelExtensionUtils.isSupportedNamespace(ModelExtensionUtils.java:533) > at org.teiid.designer.core.extension.EmfModelObjectExtensionAssistant.supportsMyNamespace(EmfModelObjectExtensionAssistant.java:598) > at org.teiid.designer.metamodels.relational.extension.RelationalModelExtensionAssistant.applyMedIfNecessary(RelationalModelExtensionAssistant.java:94) > at org.teiid.designer.metamodels.relational.RelationalPlugin.handleNewModelEvent(RelationalPlugin.java:208) > at org.teiid.designer.metamodels.relational.RelationalPlugin$2.notifyAdd(RelationalPlugin.java:174) > at org.teiid.designer.core.workspace.ModelWorkspaceManager.fire(ModelWorkspaceManager.java:631) > at org.teiid.designer.core.workspace.DeltaProcessor.fireNotification(DeltaProcessor.java:140) > at org.teiid.designer.core.workspace.DeltaProcessor.resourceChanged(DeltaProcessor.java:70) > at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285) > at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149) > at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:378) > at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1498) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:45) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > Caused by: org.xml.sax.SAXParseExceptionpublicId: file:/C:/Users/dv/workspaces/jbds-8.1.0.GA_jbdsis-8.0.2.CR1/ModelRefactoringProject/partssupplier_view_3.xmi; systemId: file:/C:/Users/dv/workspaces/jbds-8.1.0.GA_jbdsis-8.0.2.CR1/ModelRefactoringProject/partssupplier_view_3.xmi; lineNumber: 6; columnNumber: 112; Element type "modelImports" must be followed by either attribute specifications, ">" or "/>". > at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:198) > at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177) > at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:441) > at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:368) > at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1436) > at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.seekCloseOfStartTag(XMLDocumentFragmentScannerImpl.java:1395) > at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1328) > at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2786) > at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606) > at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510) > at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848) > at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777) > at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141) > at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213) > at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:648) > at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:332) > at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl.java:175) > at org.teiid.designer.core.resource.xmi.MtkXmiResourceImpl.doLoad(MtkXmiResourceImpl.java:284) > at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1518) > at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1297) > at org.teiid.designer.core.resource.xmi.MtkXmiResourceImpl.load(MtkXmiResourceImpl.java:224) > at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoad(ResourceSetImpl.java:259) > at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoadHelper(ResourceSetImpl.java:274) > ... 28 more > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues June 2015