July 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1801) Usability - When creating REST War, save the Target Data Services info to be used on subsequent creations

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1801?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1801: ----------------------------------- Fix Version/s: 8.3 > Usability - When creating REST War, save the Target Data Services info to be used on subsequent creations > --------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1801 > URL: https://issues.jboss.org/browse/TEIIDDES-1801 > Project: Teiid Designer > Issue Type: Enhancement > Components: Dialogs > Affects Versions: 8.2 > Reporter: Van Halbert > Assignee: Ted Jones > Priority: Minor > Fix For: 8.3 > > > When creating the REST War, the Target DataServices info (i.e., jar locations) should be saved for subsequent creations so that the user doesn't have to browse for the locations a second time. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1730) When creating datasource for Teiid VDB, default to using local Teiid connection

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1730?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1730: ---------------------------------------- Paul, can you take a look at Van's request? > When creating datasource for Teiid VDB, default to using local Teiid connection > ------------------------------------------------------------------------------- > > Key: TEIIDDES-1730 > URL: https://issues.jboss.org/browse/TEIIDDES-1730 > Project: Teiid Designer > Issue Type: Feature Request > Components: Teiid Integration, Usability > Affects Versions: 7.8 > Reporter: Van Halbert > Assignee: Paul Richardson > > From a usability issue, it would good if the default Teiid URL defined in the datasource that is created on the server is for the local connection. IMO, majority of the time when a Teiid datasource is defined in the server if for a local connection to be used by web applications or integration with other components (i.e, ESB) that will access Teiid via JNDI. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1801) Usability - When creating REST War, save the Target Data Services info to be used on subsequent creations

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1801?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1801: ----------------------------------- Assignee: Ted Jones (was: Barry LaFond) > Usability - When creating REST War, save the Target Data Services info to be used on subsequent creations > --------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1801 > URL: https://issues.jboss.org/browse/TEIIDDES-1801 > Project: Teiid Designer > Issue Type: Enhancement > Components: Dialogs > Affects Versions: 8.2 > Reporter: Van Halbert > Assignee: Ted Jones > Priority: Minor > > When creating the REST War, the Target DataServices info (i.e., jar locations) should be saved for subsequent creations so that the user doesn't have to browse for the locations a second time. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1730) When creating datasource for Teiid VDB, default to using local Teiid connection

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1730?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1730: ----------------------------------- Assignee: Paul Richardson > When creating datasource for Teiid VDB, default to using local Teiid connection > ------------------------------------------------------------------------------- > > Key: TEIIDDES-1730 > URL: https://issues.jboss.org/browse/TEIIDDES-1730 > Project: Teiid Designer > Issue Type: Feature Request > Components: Teiid Integration, Usability > Affects Versions: 7.8 > Reporter: Van Halbert > Assignee: Paul Richardson > > From a usability issue, it would good if the default Teiid URL defined in the datasource that is created on the server is for the local connection. IMO, majority of the time when a Teiid datasource is defined in the server if for a local connection to be used by web applications or integration with other components (i.e, ESB) that will access Teiid via JNDI. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1774) Create Guides View Action Set for new Teiid Connection Importer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1774?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1774: ----------------------------------- Attachment: model-teiid-data-source-action-set.png > Create Guides View Action Set for new Teiid Connection Importer > --------------------------------------------------------------- > > Key: TEIIDDES-1774 > URL: https://issues.jboss.org/browse/TEIIDDES-1774 > Project: Teiid Designer > Issue Type: Feature Request > Components: Documentation, Import/Export > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.2 > > Attachments: model-teiid-data-source-action-set.png > > > Create an action set for the Teiid Connection importer. > Probably want to make it a simple Flat File or remove XML file importer so there will be no need to deploy jars to the server -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1765) StateInfo example does not succeed

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1765?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1765: ----------------------------------- Assignee: Van Halbert > StateInfo example does not succeed > ---------------------------------- > > Key: TEIIDDES-1765 > URL: https://issues.jboss.org/browse/TEIIDDES-1765 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.2 > Reporter: Van Halbert > Assignee: Van Halbert > > Walked thru the StateInfo example, and when I went to execute > 12:55:47,190 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (http-/127.0.0.1:8080-1) Interceptor for {http://www.teiid.org/stateService/}stateService#{http://www.teiid.org/stateService/}GetAllStateInfo has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Unexpected wrapper element GetAllStateInfo found. Expected {http://www.teiid.org/stateService/}GetAllStateInfo. > at org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.java:106) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:262) > at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) > at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:237) > at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:95) > at org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:156) > at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:87) > at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:225) > at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:145) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] > at org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:135) > at org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140) [jbossws-spi-2.1.2.Final-redhat-1.jar:2.1.2.Final-redhat-1] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13] > 12:55:47,195 WARN [org.teiid.CONNECTOR] (Worker7_QueryProcessorQueue27) Connector worker process failed for atomic-request=VUNHCCMa+sUf.0.9.3: org.teiid.translator.TranslatorException: Unexpected wrapper element GetAllStateInfo found. Expected {http://www.teiid.org/stateService/}GetAllStateInfo. > at org.teiid.translator.ws.WSProcedureExecution.execute(WSProcedureExecution.java:139) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:254) [teiid-engine-8.4.0.Final.jar:8.4.0.Final] > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:446) [teiid-engine-8.4.0.Final.jar:8.4.0.Final] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:159) [teiid-engine-8.4.0.Final.jar:8.4.0.Final] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:156) [teiid-engine-8.4.0.Final.jar:8.4.0.Final] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_13] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_13] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.4.0.Final.jar:8.4.0.Final] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:269) [teiid-engine-8.4.0.Final.jar:8.4.0.Final] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.4.0.Final.jar:8.4.0.Final] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.4.0.Final.jar:8.4.0.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13] > Caused by: javax.xml.ws.soap.SOAPFaultException: Unexpected wrapper element GetAllStateInfo found. Expected {http://www.teiid.org/stateService/}GetAllStateInfo. > at org.apache.cxf.jaxws.DispatchImpl.mapException(DispatchImpl.java:287) > at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:392) > at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:243) > at org.teiid.translator.ws.WSProcedureExecution.execute(WSProcedureExecution.java:135) > ... 13 more > Caused by: org.apache.cxf.binding.soap.SoapFault: Unexpected wrapper element GetAllStateInfo found. Expected {http://www.teiid.org/stateService/}GetAllStateInfo. > at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.unmarshalFault(Soap11FaultInInterceptor.java:75) > at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:46) > at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:35) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:262) > at org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:114) > at org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:69) > at org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:34) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:262) > at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:800) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1696) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1532) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1440) > at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56) > at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:659) > at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:262) > at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:530) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:463) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:366) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:319) > at org.apache.cxf.endpoint.ClientImpl.invokeWrapped(ClientImpl.java:354) > at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:385) > ... 15 more > 12:55:47,199 WARN [org.teiid.PROCESSOR] (Worker6_QueryProcessorQueue28) TEIID30020 Processing exception for request VUNHCCMa+sUf.0 'TEIID30504 stateService: Unexpected wrapper element GetAllStateInfo found. Expected {http://www.teiid.org/stateService/}GetAllStateInfo.'. Originally TeiidProcessingException Soap11FaultInInterceptor.java:75. Enable more detailed logging to see the entire stacktrace. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1774) Create Guides View Action Set for new Teiid Connection Importer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1774?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1774. ------------------------------------ Resolution: Done Done > Create Guides View Action Set for new Teiid Connection Importer > --------------------------------------------------------------- > > Key: TEIIDDES-1774 > URL: https://issues.jboss.org/browse/TEIIDDES-1774 > Project: Teiid Designer > Issue Type: Feature Request > Components: Documentation, Import/Export > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.2 > > > Create an action set for the Teiid Connection importer. > Probably want to make it a simple Flat File or remove XML file importer so there will be no need to deploy jars to the server -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1802) NPE when trying to add Result Set to the procedure that is being created

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1802?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1802: ----------------------------------- Fix Version/s: 8.2 > NPE when trying to add Result Set to the procedure that is being created > ------------------------------------------------------------------------ > > Key: TEIIDDES-1802 > URL: https://issues.jboss.org/browse/TEIIDDES-1802 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs > Affects Versions: 8.2 > Reporter: Van Halbert > Assignee: Barry LaFond > Priority: Critical > Fix For: 8.2 > > > When in the create procedure dialog, unable to press the Result Set tab. > Produces the NPE: > java.lang.NullPointerException > at org.teiid.designer.transformation.ui.editors.ViewProcedureEditorPanel$3.widgetSelected(ViewProcedureEditorPanel.java:298) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4166) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489) > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1749) Extension Properties in Table Editor incorrect

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1749?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1749: ----------------------------------- Assignee: Mark Drilling (was: Dan Florian) > Extension Properties in Table Editor incorrect > ---------------------------------------------- > > Key: TEIIDDES-1749 > URL: https://issues.jboss.org/browse/TEIIDDES-1749 > Project: Teiid Designer > Issue Type: Bug > Components: Editors, Extension Framework > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Mark Drilling > Priority: Critical > Fix For: 8.2 > > > * Created 2 or more tables in relational model > * Edit table 1's "relational:Native Query" extension property (SELECT * FROM FOOBAR) > * Save > * Open/Select Table Editor and select BASE TABLES tab > * Note that "relational:Native Query" property is same for both tables > Looks like the ModelExtensionPropertyDescriptor is caching an EObject and the call to getPropertyValue() will return the same value for ALL EObjects rather than having a unique EObject per descriptor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1289) After importing metadata using the ModeShape jdbc driver, the connection information was not propagated from the connection profile

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1289?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1289: ----------------------------------- Assignee: Mark Drilling (was: Dan Florian) > After importing metadata using the ModeShape jdbc driver, the connection information was not propagated from the connection profile > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1289 > URL: https://issues.jboss.org/browse/TEIIDDES-1289 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.7.1 > Reporter: Van Halbert > Assignee: Mark Drilling > Fix For: 8.2 > > > After importing the metadata using the modeshape jdbc driver, I created the ModeShape.vdb and tried to deploy. It wouldn't deploy because the connection information was not in the ModeShape.xmi model. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 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 July 2013