[JBoss JIRA] (TEIIDDES-1765) StateInfo example does not succeed
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1765?page=com.atlassian.jira.plu... ]
Ted Jones reassigned TEIIDDES-1765:
-----------------------------------
Assignee: Ted Jones (was: 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: Ted Jones
> Fix For: 9.0.3
>
>
> 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 was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIIDDES-303) Materialization can fail when MMX passes back data that exceeds the maximum length, as defined in the materialized model.
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-303?page=com.atlassian.jira.plug... ]
Ted Jones reassigned TEIIDDES-303:
----------------------------------
Assignee: Van Halbert
> Materialization can fail when MMX passes back data that exceeds the maximum length, as defined in the materialized model.
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-303
> URL: https://issues.jboss.org/browse/TEIIDDES-303
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 7.1
> Environment: Windows 2003 Server, 5.5 + patch 62
> Reporter: Michael Walker
> Assignee: Van Halbert
> Labels: materialization
> Fix For: 9.0.3
>
>
> When querying data from a source model, MMX allows data to exceed the model's length restrictions. For example, a SalesForce model might have a column called "biography:string(200)". Querying data from this column can sometimes result in a string that exceeds 200 characters, and MMX does not truncate the data.
> This causes problems when you attempt to materialize the model. Since the create table scripts are based on the model definition, the mat view table will not accommodate data that exceeds the length restrictions. Following the previous example, this means that the biography data will raise a "inserted length too large for column" error, causing the rest of the materialization to fail.
> The new materialization process will need to account for this issue, or perhaps MMX should truncate data that exceeds the defined length found within the model.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIIDDES-303) Materialization can fail when MMX passes back data that exceeds the maximum length, as defined in the materialized model.
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-303?page=com.atlassian.jira.plug... ]
Ted Jones commented on TEIIDDES-303:
------------------------------------
[~vhalbert], can you validate this issue is out of date?
> Materialization can fail when MMX passes back data that exceeds the maximum length, as defined in the materialized model.
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-303
> URL: https://issues.jboss.org/browse/TEIIDDES-303
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 7.1
> Environment: Windows 2003 Server, 5.5 + patch 62
> Reporter: Michael Walker
> Assignee: Van Halbert
> Labels: materialization
> Fix For: 9.0.3
>
>
> When querying data from a source model, MMX allows data to exceed the model's length restrictions. For example, a SalesForce model might have a column called "biography:string(200)". Querying data from this column can sometimes result in a string that exceeds 200 characters, and MMX does not truncate the data.
> This causes problems when you attempt to materialize the model. Since the create table scripts are based on the model definition, the mat view table will not accommodate data that exceeds the length restrictions. Following the previous example, this means that the biography data will raise a "inserted length too large for column" error, causing the rest of the materialization to fail.
> The new materialization process will need to account for this issue, or perhaps MMX should truncate data that exceeds the defined length found within the model.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIIDDES-303) Materialization can fail when MMX passes back data that exceeds the maximum length, as defined in the materialized model.
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-303?page=com.atlassian.jira.plug... ]
Ted Jones updated TEIIDDES-303:
-------------------------------
Fix Version/s: 9.0.3
> Materialization can fail when MMX passes back data that exceeds the maximum length, as defined in the materialized model.
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-303
> URL: https://issues.jboss.org/browse/TEIIDDES-303
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 7.1
> Environment: Windows 2003 Server, 5.5 + patch 62
> Reporter: Michael Walker
> Assignee: Van Halbert
> Labels: materialization
> Fix For: 9.0.3
>
>
> When querying data from a source model, MMX allows data to exceed the model's length restrictions. For example, a SalesForce model might have a column called "biography:string(200)". Querying data from this column can sometimes result in a string that exceeds 200 characters, and MMX does not truncate the data.
> This causes problems when you attempt to materialize the model. Since the create table scripts are based on the model definition, the mat view table will not accommodate data that exceeds the length restrictions. Following the previous example, this means that the biography data will raise a "inserted length too large for column" error, causing the rest of the materialization to fail.
> The new materialization process will need to account for this issue, or perhaps MMX should truncate data that exceeds the defined length found within the model.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIIDDES-2325) REST Importer: Inline edit the parameters
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2325?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-2325:
--------------------------------
Fix Version/s: Komodo
> REST Importer: Inline edit the parameters
> -----------------------------------------
>
> Key: TEIIDDES-2325
> URL: https://issues.jboss.org/browse/TEIIDDES-2325
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Affects Versions: 8.6
> Reporter: Ramesh Reddy
> Assignee: Ted Jones
> Fix For: Komodo
>
> Attachments: popup.png
>
>
> When using REST importer (actually goes for any dialog), when user is trying to add parameter it is done as POP-UP, that is 4th layer counting original layout. I believe this level can be removed by inline editing on the table in layer 3, see the attached picture.
> I guess I draw line at 4th level :) hehe
> Also, currently in layer 3 the user is given editing choices in the table but once the focus is gone the value is restored to previous value (this is a bug)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIIDDES-2504) Able to enter freeform input in Type field of "Add new parameter" dialog in "Web Services Data Source (REST)" connection profile
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2504?page=com.atlassian.jira.plu... ]
Ted Jones resolved TEIIDDES-2504.
---------------------------------
Resolution: Out of Date
Fixed with previous Jira
> Able to enter freeform input in Type field of "Add new parameter" dialog in "Web Services Data Source (REST)" connection profile
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2504
> URL: https://issues.jboss.org/browse/TEIIDDES-2504
> Project: Teiid Designer
> Issue Type: Bug
> Components: Web Services Support
> Affects Versions: 9.0
> Environment: Mac, Linux
> JBDS Version: 8.0.0.GA
> Build id: GA-v20141020-1042-B317
> Teiid Designer version: 9.0.1.Final-v20150211-1407-B643
> Reporter: Marc Shirley
> Assignee: Ted Jones
>
> When creating/editing connection profile to add a new parameter to a REST service, able to enter freeform text in the Type field of the "Add New Parameter" popup dialog. However, the freeform value returns to the previously selected value (Query or URI) when OK is clicked. Either the field should be unable to be modified, or the value entered should be preserved.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIIDDES-2506) NPE when attempting to finish REST import
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2506?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-2506:
--------------------------------
Fix Version/s: Komodo
(was: 9.2)
(was: 9.0.3)
> NPE when attempting to finish REST import
> -----------------------------------------
>
> Key: TEIIDDES-2506
> URL: https://issues.jboss.org/browse/TEIIDDES-2506
> Project: Teiid Designer
> Issue Type: Bug
> Components: Web Services Support
> Affects Versions: 9.0
> Environment: Mac
> JBDS Version: 8.0.0.GA
> Build id: GA-v20141020-1042-B317
> Teiid Designer version: 9.0.1.Final-v20150211-1407-B643
> Reporter: Marc Shirley
> Assignee: Ted Jones
> Fix For: Komodo
>
>
> Popup dialog when finishing REST import wizard with content:
> "Error creating view model ViewModel.xmi" with error text "Failed to execute runnable (org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException))"
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIIDDES-2052) 'Mark as Deployable' on a war not working for remote (OpenShift) server
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2052?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-2052:
--------------------------------
Fix Version/s: 9.0.3
> 'Mark as Deployable' on a war not working for remote (OpenShift) server
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-2052
> URL: https://issues.jboss.org/browse/TEIIDDES-2052
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.3.1
> Reporter: Mark Drilling
> Assignee: Mark Drilling
> Fix For: 9.2, 9.0.3
>
>
> I created a war (using Rest War generator) in Designer and added it to my project. Then to deploy it, I selected it and used the 'Mark as Deployable" action.
> This worked fine on my local server (both deploy and undeploy) but then I switched to an OpenShift external server instance (used port-forwarding).
> The 'Mark as Deployable' action doesnt work for the Openshift external server. Maybe the action is doing a copy of the war into the deployments folder?
> We don't provide the action, but we should either troubleshoot or potentially provide our own action which deploys a war using the admin api.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months