[JBoss JIRA] (TEIIDDES-1765) StateInfo example does not succeed
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1765?page=com.atlassian.jira.plu... ]
Paul Richardson commented on TEIIDDES-1765:
-------------------------------------------
Not necessarily. Having played with state info extensively, you might find its actually a namespace issue. I originally corrected it with the change detailed [here|https://github.com/phantomjinx/teiid-soap-example/commit/c3bf73fe4cf...].
You can try downloading and using the version published at [https://github.com/phantomjinx/teiid-soap-example] and see if that works.
> 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
>
> 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
[JBoss JIRA] (TEIIDDES-1101) Datatype Resolver Dialog sizing may hide buttons
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1101?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1101.
------------------------------------
Resolution: Out of Date
Datatype resolver dialog was re-written to take a different approach and has eliminated these issues.
> Datatype Resolver Dialog sizing may hide buttons
> ------------------------------------------------
>
> Key: TEIIDDES-1101
> URL: https://issues.jboss.org/browse/TEIIDDES-1101
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dialogs
> Affects Versions: 7.5
> Environment: RHEL6-32 JBDS 4.1.1 M2
> Reporter: Paul Nittel
> Priority: Minor
> Fix For: Future
>
> Attachments: TypeResolverSizing.png
>
>
> I'm running the Designer in an admittedly small window (virtual machine in my case, but it could just be a laptop thing). When the type resolver first displays, the buttons to convert the SQL Symbol are hidden. There is a vertical scroll bar, but when scrolled to the bottom, the buttons are only slightly revealed.
> If we could ensure the buttons would be completely visible by either scrolling or resizing the bottom section of the dialog (can't; it's all fixed), it would make for a better user experience.
> Screenshot attached.
--
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
[JBoss JIRA] (TEIIDDES-1079) Create Import VDB wizard
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1079?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1079:
----------------------------------------
Extracting models from a VDB feature is allowed via Quick Fix action contributed in TEIIDDES-1611.
It's not a straight forward technique but does address some concerns above around conflicting models in workspace. VDB validation now does provide some level of keeping VDB's and workspace models in sync.
> Create Import VDB wizard
> ------------------------
>
> Key: TEIIDDES-1079
> URL: https://issues.jboss.org/browse/TEIIDDES-1079
> Project: Teiid Designer
> Issue Type: Sub-task
> Components: Editors, Modeling, VDB & Execution
> Affects Versions: 7.5
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: Future
>
>
> For usability improvements and migration support, it would be great to be able to import a VDB into a workspace, extract the models from the VDB into a new project (along with the VDB) and allow the user to begin to start editing the models as if they were new.
> Secondary thoughts:
> - Should Translator Override properties be extractable from a VDB so users can apply them to multiple VDB's?
> - Then should the Translator Overrides action and editor be available in Teiid Designer outside the VDB Editor??
> - Should anything be done with Data Roles so they are transferable between VDB's?
> - Do we need a Clone VDB action? which would clone the resources, vdb.xml contents, but re-index the files?
> - How do we handle extracting/importing models from VDB that already exist in the workspace?
> < First cut would maybe prevent user from extracting any models if any model conflicts exist.
--
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
[JBoss JIRA] (TEIIDDES-1707) Data Source Created Using Model Connection Info Does Not Work
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1707?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1707:
----------------------------------------
So one aspect of this issue is that a Data Source with incomplete URL is actually deployed through Teiid/Server. Should this be possible? or isn't the server that smart?
> Data Source Created Using Model Connection Info Does Not Work
> -------------------------------------------------------------
>
> Key: TEIIDDES-1707
> URL: https://issues.jboss.org/browse/TEIIDDES-1707
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.1
> Reporter: Dan Florian
>
> I did a JDBC import that created a relational model. I right-clicked on the new model and Modeling > Create Data Source. On the Create Data Source dialog I entered a data source name and left every other value untouched. I had to enter a password after that dialog closed. Using the newly created data source in a Teiid Connection import fails because the URL of the data source does not have the database name.
--
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
[JBoss JIRA] (TEIIDDES-1428) Unable to create multiple Teiid Server Connection profiles pointing to the same server
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1428?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1428:
----------------------------------------
Paul, can you comment on whether this is fixed or not and whether we want to if not?
> Unable to create multiple Teiid Server Connection profiles pointing to the same server
> --------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1428
> URL: https://issues.jboss.org/browse/TEIIDDES-1428
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview, Usability
> Affects Versions: 7.7
> Reporter: Van Halbert
> Assignee: Paul Richardson
> Fix For: 8.2
>
>
> Teiid Server connection instances are identified by a unique name assigned by the user. However, it appears there's an internal url validation being done that will not allow me to create multiple instances pointing to the same server. I would think it shouldn't care what url I use, as long as the instance name is unique.
> And it could be useful to test different jdbc connections to the same server, but this rule would not allow that. I would suggest turning off any rule that compares a Teiid Server instance setup.
--
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
[JBoss JIRA] (TEIIDDES-1428) Unable to create multiple Teiid Server Connection profiles pointing to the same server
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1428?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1428:
-----------------------------------
Assignee: Paul Richardson
> Unable to create multiple Teiid Server Connection profiles pointing to the same server
> --------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1428
> URL: https://issues.jboss.org/browse/TEIIDDES-1428
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview, Usability
> Affects Versions: 7.7
> Reporter: Van Halbert
> Assignee: Paul Richardson
> Fix For: 8.2
>
>
> Teiid Server connection instances are identified by a unique name assigned by the user. However, it appears there's an internal url validation being done that will not allow me to create multiple instances pointing to the same server. I would think it shouldn't care what url I use, as long as the instance name is unique.
> And it could be useful to test different jdbc connections to the same server, but this rule would not allow that. I would suggest turning off any rule that compares a Teiid Server instance setup.
--
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
[JBoss JIRA] (TEIIDDES-1428) Unable to create multiple Teiid Server Connection profiles pointing to the same server
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1428?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1428:
-----------------------------------
Fix Version/s: 8.2
> Unable to create multiple Teiid Server Connection profiles pointing to the same server
> --------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1428
> URL: https://issues.jboss.org/browse/TEIIDDES-1428
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview, Usability
> Affects Versions: 7.7
> Reporter: Van Halbert
> Fix For: 8.2
>
>
> Teiid Server connection instances are identified by a unique name assigned by the user. However, it appears there's an internal url validation being done that will not allow me to create multiple instances pointing to the same server. I would think it shouldn't care what url I use, as long as the instance name is unique.
> And it could be useful to test different jdbc connections to the same server, but this rule would not allow that. I would suggest turning off any rule that compares a Teiid Server instance setup.
--
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