[JBoss JIRA] (TEIIDDES-1738) Data role editor modifications can result in duplicate roles being generated.
by Johnathon Lee (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1738?page=com.atlassian.jira.plu... ]
Johnathon Lee resolved TEIIDDES-1738.
-------------------------------------
Resolution: Done
> Data role editor modifications can result in duplicate roles being generated.
> -----------------------------------------------------------------------------
>
> Key: TEIIDDES-1738
> URL: https://issues.jboss.org/browse/TEIIDDES-1738
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 7.7.3
> Environment: This appears to be more prominent on Windows, but duplicate roles have been observed on both Windows and Linux machines.
> Reporter: Marc Shirley
> Assignee: Johnathon Lee
> Fix For: 8.2, 7.7.4
>
> Attachments: org.teiid.designer.roles.ui.patch
>
>
> Editing the data roles through the VDB data roles editor can result in duplicate roles being generated, or the roles not being saved correctly in the current active copy of the role. Observed effects:
> 1) duplicate roles appearing
> 2) permissions being reset after VDB synchronization
> 3) duplicate roles appearing after attempting to delete a role
--
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
10 years, 10 months
[JBoss JIRA] (TEIIDDES-1766) Cannot preview WSDL webservice
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1766?page=com.atlassian.jira.plu... ]
Paul Richardson commented on TEIIDDES-1766:
-------------------------------------------
This is also applicable to file-based connection factories hence impossible to preview any part of the BrokerageModel in the FinancialsDemo.
> Cannot preview WSDL webservice
> ------------------------------
>
> Key: TEIIDDES-1766
> URL: https://issues.jboss.org/browse/TEIIDDES-1766
> Project: Teiid Designer
> Issue Type: Bug
> Components: Web Services Support
> Affects Versions: 8.2
> Reporter: Paul Richardson
> Assignee: Ted Jones
> Fix For: 8.2
>
>
> When trying to preview a model that includes a WSDL webservice as a source, the process fails due to the following error:
> {code}
> org.teiid.adminapi.AdminProcessingException: TEIID70003 Data source with name PREVIEW_2dd455bc-3423-4866-a362-3e5cd83831cb_FinancialsDemo_VirtualBaseLayer_StockQuote_sources_StockQuote already exists; choose a different deployment name
> {code}
> Stacktrace:
> {code}
> at org.teiid.adminapi.AdminFactory$AdminImpl.createDataSource(AdminFactory.java:407)
> at org.teiid84.runtime.ExecutionAdmin.getOrCreateDataSource(ExecutionAdmin.java:324)
> at org.teiid.designer.runtime.TeiidServer.getOrCreateDataSource(TeiidServer.java:551)
> at org.teiid.designer.runtime.TeiidDataSourceFactory.createDataSource(TeiidDataSourceFactory.java:107)
> at org.teiid.designer.runtime.preview.PreviewManager.getOrCreateDataSource(PreviewManager.java:667)
> at org.teiid.designer.runtime.preview.PreviewManager.ensureConnectionInfoIsValid(PreviewManager.java:504)
> {code}
> The error is right that a PREVIEW already exists and the getOrCreateDataSource() method is wrong is trying to create it. The webservice PREVIEWs are held in the:
> {code}
> <subsystem>
> <resource-adapters>
> <resource-adapter id="webservice">
> ...
> </resource-adapter>
> </resource-adapters>
> </subsystem>
> {code}
> rather than with the datasources and these are never checked or cached by Designer.
> Likewise these previews never appear in the server view under datasources since they are never returned via ExecutionAdmin.refreshDataSourceNames().
> Question is how to properly refactor ExecutionAdmin classes to correctly return these data sources (that are not technically data sources) so that getOrCreate works as does delete.
> Note. the webservice data source does appear in the server view but the preview does not!
--
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
10 years, 10 months
[JBoss JIRA] (TEIIDDES-1766) Cannot preview WSDL webservice
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1766?page=com.atlassian.jira.plu... ]
Paul Richardson commented on TEIIDDES-1766:
-------------------------------------------
Further investigation shows that designer's logic is sound...
Designer defers to AdminFactory.AdminImpl.getDataSourceNames() which in turn calls getConnectionFactoryNames() -> getRAConnections(). The latter method in the teiid client is responsible for collecting the webservice preview connections but seemingly returns nothing.
Interestingly, despite the configuration file (standalone-teiid.xml) being rewritten to include all the other VDB preview components, the webservice preview is missing. Thus, presumably a case of JBoss having inserted the preview in one cache but not fully installed it ... or JBoss not having completely removed it previously hence a similar caching issue to [https://issues.jboss.org/browse/TEIIDDES-1767].
> Cannot preview WSDL webservice
> ------------------------------
>
> Key: TEIIDDES-1766
> URL: https://issues.jboss.org/browse/TEIIDDES-1766
> Project: Teiid Designer
> Issue Type: Bug
> Components: Web Services Support
> Affects Versions: 8.2
> Reporter: Paul Richardson
> Assignee: Ted Jones
> Fix For: 8.2
>
>
> When trying to preview a model that includes a WSDL webservice as a source, the process fails due to the following error:
> {code}
> org.teiid.adminapi.AdminProcessingException: TEIID70003 Data source with name PREVIEW_2dd455bc-3423-4866-a362-3e5cd83831cb_FinancialsDemo_VirtualBaseLayer_StockQuote_sources_StockQuote already exists; choose a different deployment name
> {code}
> Stacktrace:
> {code}
> at org.teiid.adminapi.AdminFactory$AdminImpl.createDataSource(AdminFactory.java:407)
> at org.teiid84.runtime.ExecutionAdmin.getOrCreateDataSource(ExecutionAdmin.java:324)
> at org.teiid.designer.runtime.TeiidServer.getOrCreateDataSource(TeiidServer.java:551)
> at org.teiid.designer.runtime.TeiidDataSourceFactory.createDataSource(TeiidDataSourceFactory.java:107)
> at org.teiid.designer.runtime.preview.PreviewManager.getOrCreateDataSource(PreviewManager.java:667)
> at org.teiid.designer.runtime.preview.PreviewManager.ensureConnectionInfoIsValid(PreviewManager.java:504)
> {code}
> The error is right that a PREVIEW already exists and the getOrCreateDataSource() method is wrong is trying to create it. The webservice PREVIEWs are held in the:
> {code}
> <subsystem>
> <resource-adapters>
> <resource-adapter id="webservice">
> ...
> </resource-adapter>
> </resource-adapters>
> </subsystem>
> {code}
> rather than with the datasources and these are never checked or cached by Designer.
> Likewise these previews never appear in the server view under datasources since they are never returned via ExecutionAdmin.refreshDataSourceNames().
> Question is how to properly refactor ExecutionAdmin classes to correctly return these data sources (that are not technically data sources) so that getOrCreate works as does delete.
> Note. the webservice data source does appear in the server view but the preview does not!
--
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
10 years, 10 months
[JBoss JIRA] (TEIIDDES-1767) Cannot redeploy a vdb with webservice datasource
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1767?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-1767:
----------------------------------------
see https://issues.jboss.org/browse/TEIID-2035 for a long standing issue with connection factories in AS 7
> Cannot redeploy a vdb with webservice datasource
> ------------------------------------------------
>
> Key: TEIIDDES-1767
> URL: https://issues.jboss.org/browse/TEIIDDES-1767
> Project: Teiid Designer
> Issue Type: Bug
> Reporter: Paul Richardson
> Assignee: Ted Jones
>
> When redeploying a vdb that contains a WSDL webservice, the following behaviour is observed.
> 1. Delete all vdb's data sources, including the WSDL webservice data source;
> 2. Deploy the vdb
> 3. Observe the following error
> {code}
> !ENTRY org.teiid.designer.dqp.ui 4 0 2013-06-27 10:18:06.314
> !MESSAGE TEIID70006 JBAS014749: Operation handler failed: Service jboss.resourceadapters.ra.webservice.StockQuote is already registered
> !STACK 0
> org.teiid.adminapi.AdminProcessingException: TEIID70006 JBAS014749: Operation handler failed: Service jboss.resourceadapters.ra.webservice.StockQuote is already registered
> at org.teiid.adminapi.AdminFactory$ResultCallback.onFailure(AdminFactory.java:195)
> at org.teiid.adminapi.AdminFactory$AdminImpl.cliCall(AdminFactory.java:1409)
> at org.teiid.adminapi.AdminFactory$AdminImpl.createConnectionFactory(AdminFactory.java:277)
> at org.teiid.adminapi.AdminFactory$AdminImpl.createDataSource(AdminFactory.java:412)
> at org.teiid84.runtime.ExecutionAdmin.getOrCreateDataSource(ExecutionAdmin.java:324)
> at org.teiid.designer.runtime.TeiidServer.getOrCreateDataSource(TeiidServer.java:551)
> at org.teiid.designer.runtime.TeiidDataSourceFactory.createDataSource(TeiidDataSourceFactory.java:107)
> at org.teiid.designer.runtime.ui.vdb.VdbDeployer.deploy(VdbDeployer.java:239)
> at org.teiid.designer.runtime.ui.actions.DeployVdbAction$1.run(DeployVdbAction.java:286)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> {code}
> Despite 'StockQuote' being deleted in step 1, the JBoss server still has it cached in a map so throws back this error. The client does not show it and connecting to the server via the cli also fails to show it. Restarting the server flushes the cache and the vdb can be successfully redeployed.
> Whether this should be passed to Teiid (are they responsible for flushing the cache?) or WireFly (not properly flushing the cache or data source deletion) is the question...
--
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
10 years, 10 months
[JBoss JIRA] (TEIIDDES-1767) Cannot redeploy a vdb with webservice datasource
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1767?page=com.atlassian.jira.plu... ]
Paul Richardson edited comment on TEIIDDES-1767 at 6/27/13 6:56 AM:
--------------------------------------------------------------------
These may have a relationship since they both pass through getOrCreateDataSource. However, the client seems to understand that the data source has gone so I think the caching issue is further down the stack (Teiid/JBoss).
was (Author: phantomjinx):
These may have a relationship since they both pass through getOrCreateDataSource but there is certainly a caching issue present.
> Cannot redeploy a vdb with webservice datasource
> ------------------------------------------------
>
> Key: TEIIDDES-1767
> URL: https://issues.jboss.org/browse/TEIIDDES-1767
> Project: Teiid Designer
> Issue Type: Bug
> Reporter: Paul Richardson
> Assignee: Ted Jones
>
> When redeploying a vdb that contains a WSDL webservice, the following behaviour is observed.
> 1. Delete all vdb's data sources, including the WSDL webservice data source;
> 2. Deploy the vdb
> 3. Observe the following error
> {code}
> !ENTRY org.teiid.designer.dqp.ui 4 0 2013-06-27 10:18:06.314
> !MESSAGE TEIID70006 JBAS014749: Operation handler failed: Service jboss.resourceadapters.ra.webservice.StockQuote is already registered
> !STACK 0
> org.teiid.adminapi.AdminProcessingException: TEIID70006 JBAS014749: Operation handler failed: Service jboss.resourceadapters.ra.webservice.StockQuote is already registered
> at org.teiid.adminapi.AdminFactory$ResultCallback.onFailure(AdminFactory.java:195)
> at org.teiid.adminapi.AdminFactory$AdminImpl.cliCall(AdminFactory.java:1409)
> at org.teiid.adminapi.AdminFactory$AdminImpl.createConnectionFactory(AdminFactory.java:277)
> at org.teiid.adminapi.AdminFactory$AdminImpl.createDataSource(AdminFactory.java:412)
> at org.teiid84.runtime.ExecutionAdmin.getOrCreateDataSource(ExecutionAdmin.java:324)
> at org.teiid.designer.runtime.TeiidServer.getOrCreateDataSource(TeiidServer.java:551)
> at org.teiid.designer.runtime.TeiidDataSourceFactory.createDataSource(TeiidDataSourceFactory.java:107)
> at org.teiid.designer.runtime.ui.vdb.VdbDeployer.deploy(VdbDeployer.java:239)
> at org.teiid.designer.runtime.ui.actions.DeployVdbAction$1.run(DeployVdbAction.java:286)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> {code}
> Despite 'StockQuote' being deleted in step 1, the JBoss server still has it cached in a map so throws back this error. The client does not show it and connecting to the server via the cli also fails to show it. Restarting the server flushes the cache and the vdb can be successfully redeployed.
> Whether this should be passed to Teiid (are they responsible for flushing the cache?) or WireFly (not properly flushing the cache or data source deletion) is the question...
--
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
10 years, 10 months
[JBoss JIRA] (TEIIDDES-1767) Cannot redeploy a vdb with webservice datasource
by Paul Richardson (JIRA)
Paul Richardson created TEIIDDES-1767:
-----------------------------------------
Summary: Cannot redeploy a vdb with webservice datasource
Key: TEIIDDES-1767
URL: https://issues.jboss.org/browse/TEIIDDES-1767
Project: Teiid Designer
Issue Type: Bug
Reporter: Paul Richardson
Assignee: Ted Jones
When redeploying a vdb that contains a WSDL webservice, the following behaviour is observed.
1. Delete all vdb's data sources, including the WSDL webservice data source;
2. Deploy the vdb
3. Observe the following error
{code}
!ENTRY org.teiid.designer.dqp.ui 4 0 2013-06-27 10:18:06.314
!MESSAGE TEIID70006 JBAS014749: Operation handler failed: Service jboss.resourceadapters.ra.webservice.StockQuote is already registered
!STACK 0
org.teiid.adminapi.AdminProcessingException: TEIID70006 JBAS014749: Operation handler failed: Service jboss.resourceadapters.ra.webservice.StockQuote is already registered
at org.teiid.adminapi.AdminFactory$ResultCallback.onFailure(AdminFactory.java:195)
at org.teiid.adminapi.AdminFactory$AdminImpl.cliCall(AdminFactory.java:1409)
at org.teiid.adminapi.AdminFactory$AdminImpl.createConnectionFactory(AdminFactory.java:277)
at org.teiid.adminapi.AdminFactory$AdminImpl.createDataSource(AdminFactory.java:412)
at org.teiid84.runtime.ExecutionAdmin.getOrCreateDataSource(ExecutionAdmin.java:324)
at org.teiid.designer.runtime.TeiidServer.getOrCreateDataSource(TeiidServer.java:551)
at org.teiid.designer.runtime.TeiidDataSourceFactory.createDataSource(TeiidDataSourceFactory.java:107)
at org.teiid.designer.runtime.ui.vdb.VdbDeployer.deploy(VdbDeployer.java:239)
at org.teiid.designer.runtime.ui.actions.DeployVdbAction$1.run(DeployVdbAction.java:286)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
{code}
Despite 'StockQuote' being deleted in step 1, the JBoss server still has it cached in a map so throws back this error. The client does not show it and connecting to the server via the cli also fails to show it. Restarting the server flushes the cache and the vdb can be successfully redeployed.
Whether this should be passed to Teiid (are they responsible for flushing the cache?) or WireFly (not properly flushing the cache or data source deletion) is the question...
--
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
10 years, 10 months
[JBoss JIRA] (TEIIDDES-1766) Cannot preview WSDL webservice
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1766?page=com.atlassian.jira.plu... ]
Paul Richardson updated TEIIDDES-1766:
--------------------------------------
Description:
When trying to preview a model that includes a WSDL webservice as a source, the process fails due to the following error:
{code}
org.teiid.adminapi.AdminProcessingException: TEIID70003 Data source with name PREVIEW_2dd455bc-3423-4866-a362-3e5cd83831cb_FinancialsDemo_VirtualBaseLayer_StockQuote_sources_StockQuote already exists; choose a different deployment name
{code}
Stacktrace:
{code}
at org.teiid.adminapi.AdminFactory$AdminImpl.createDataSource(AdminFactory.java:407)
at org.teiid84.runtime.ExecutionAdmin.getOrCreateDataSource(ExecutionAdmin.java:324)
at org.teiid.designer.runtime.TeiidServer.getOrCreateDataSource(TeiidServer.java:551)
at org.teiid.designer.runtime.TeiidDataSourceFactory.createDataSource(TeiidDataSourceFactory.java:107)
at org.teiid.designer.runtime.preview.PreviewManager.getOrCreateDataSource(PreviewManager.java:667)
at org.teiid.designer.runtime.preview.PreviewManager.ensureConnectionInfoIsValid(PreviewManager.java:504)
{code}
The error is right that a PREVIEW already exists and the getOrCreateDataSource() method is wrong is trying to create it. The webservice PREVIEWs are held in the:
{code}
<subsystem>
<resource-adapters>
<resource-adapter id="webservice">
...
</resource-adapter>
</resource-adapters>
</subsystem>
{code}
rather than with the datasources and these are never checked or cached by Designer.
Likewise these previews never appear in the server view under datasources since they are never returned via ExecutionAdmin.refreshDataSourceNames().
Question is how to properly refactor ExecutionAdmin classes to correctly return these data sources (that are not technically data sources) so that getOrCreate works as does delete.
Note. the webservice data source does appear in the server view but the preview does not!
was:
When trying to preview a model that includes a WSDL webservice as a source, the process fails due to the following error:
{code}
org.teiid.adminapi.AdminProcessingException: TEIID70003 Data source with name PREVIEW_2dd455bc-3423-4866-a362-3e5cd83831cb_FinancialsDemo_VirtualBaseLayer_StockQuote_sources_StockQuote already exists; choose a different deployment name
{code}
Stacktrace:
{code}
at org.teiid.adminapi.AdminFactory$AdminImpl.createDataSource(AdminFactory.java:407)
at org.teiid84.runtime.ExecutionAdmin.getOrCreateDataSource(ExecutionAdmin.java:324)
at org.teiid.designer.runtime.TeiidServer.getOrCreateDataSource(TeiidServer.java:551)
at org.teiid.designer.runtime.TeiidDataSourceFactory.createDataSource(TeiidDataSourceFactory.java:107)
at org.teiid.designer.runtime.preview.PreviewManager.getOrCreateDataSource(PreviewManager.java:667)
at org.teiid.designer.runtime.preview.PreviewManager.ensureConnectionInfoIsValid(PreviewManager.java:504)
{code}
The error is right that a PREVIEW already exists and the getOrCreateDataSource() method is wrong is trying to create it. The webservice PREVIEWs are held in the:
{code}
<subsystem>
<resource-adapters>
<resource-adapter id="webservice">
...
</resource-adapter>
</resource-adapters>
</subsystem>
{code}
rather than with the datasources and these are never checked or cached by Designer.
Likewise these previews never appear in the server view under datasources since they are never returned via ExecutionAdmin.refreshDataSourceNames().
Question is how to properly refactor ExecutionAdmin classes to correctly return these data sources (that are not technically data sources) so that getOrCreate works as does delete.
> Cannot preview WSDL webservice
> ------------------------------
>
> Key: TEIIDDES-1766
> URL: https://issues.jboss.org/browse/TEIIDDES-1766
> Project: Teiid Designer
> Issue Type: Bug
> Components: Web Services Support
> Affects Versions: 8.2
> Reporter: Paul Richardson
> Assignee: Ted Jones
> Fix For: 8.2
>
>
> When trying to preview a model that includes a WSDL webservice as a source, the process fails due to the following error:
> {code}
> org.teiid.adminapi.AdminProcessingException: TEIID70003 Data source with name PREVIEW_2dd455bc-3423-4866-a362-3e5cd83831cb_FinancialsDemo_VirtualBaseLayer_StockQuote_sources_StockQuote already exists; choose a different deployment name
> {code}
> Stacktrace:
> {code}
> at org.teiid.adminapi.AdminFactory$AdminImpl.createDataSource(AdminFactory.java:407)
> at org.teiid84.runtime.ExecutionAdmin.getOrCreateDataSource(ExecutionAdmin.java:324)
> at org.teiid.designer.runtime.TeiidServer.getOrCreateDataSource(TeiidServer.java:551)
> at org.teiid.designer.runtime.TeiidDataSourceFactory.createDataSource(TeiidDataSourceFactory.java:107)
> at org.teiid.designer.runtime.preview.PreviewManager.getOrCreateDataSource(PreviewManager.java:667)
> at org.teiid.designer.runtime.preview.PreviewManager.ensureConnectionInfoIsValid(PreviewManager.java:504)
> {code}
> The error is right that a PREVIEW already exists and the getOrCreateDataSource() method is wrong is trying to create it. The webservice PREVIEWs are held in the:
> {code}
> <subsystem>
> <resource-adapters>
> <resource-adapter id="webservice">
> ...
> </resource-adapter>
> </resource-adapters>
> </subsystem>
> {code}
> rather than with the datasources and these are never checked or cached by Designer.
> Likewise these previews never appear in the server view under datasources since they are never returned via ExecutionAdmin.refreshDataSourceNames().
> Question is how to properly refactor ExecutionAdmin classes to correctly return these data sources (that are not technically data sources) so that getOrCreate works as does delete.
> Note. the webservice data source does appear in the server view but the preview does not!
--
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
10 years, 10 months
[JBoss JIRA] (TEIIDDES-1766) Cannot preview WSDL webservice
by Paul Richardson (JIRA)
Paul Richardson created TEIIDDES-1766:
-----------------------------------------
Summary: Cannot preview WSDL webservice
Key: TEIIDDES-1766
URL: https://issues.jboss.org/browse/TEIIDDES-1766
Project: Teiid Designer
Issue Type: Bug
Components: Web Services Support
Affects Versions: 8.2
Reporter: Paul Richardson
Assignee: Ted Jones
Fix For: 8.2
When trying to preview a model that includes a WSDL webservice as a source, the process fails due to the following error:
{code}
org.teiid.adminapi.AdminProcessingException: TEIID70003 Data source with name PREVIEW_2dd455bc-3423-4866-a362-3e5cd83831cb_FinancialsDemo_VirtualBaseLayer_StockQuote_sources_StockQuote already exists; choose a different deployment name
{code}
Stacktrace:
{code}
at org.teiid.adminapi.AdminFactory$AdminImpl.createDataSource(AdminFactory.java:407)
at org.teiid84.runtime.ExecutionAdmin.getOrCreateDataSource(ExecutionAdmin.java:324)
at org.teiid.designer.runtime.TeiidServer.getOrCreateDataSource(TeiidServer.java:551)
at org.teiid.designer.runtime.TeiidDataSourceFactory.createDataSource(TeiidDataSourceFactory.java:107)
at org.teiid.designer.runtime.preview.PreviewManager.getOrCreateDataSource(PreviewManager.java:667)
at org.teiid.designer.runtime.preview.PreviewManager.ensureConnectionInfoIsValid(PreviewManager.java:504)
{code}
The error is right that a PREVIEW already exists and the getOrCreateDataSource() method is wrong is trying to create it. The webservice PREVIEWs are held in the:
{code}
<subsystem>
<resource-adapters>
<resource-adapter id="webservice">
...
</resource-adapter>
</resource-adapters>
</subsystem>
{code}
rather than with the datasources and these are never checked or cached by Designer.
Likewise these previews never appear in the server view under datasources since they are never returned via ExecutionAdmin.refreshDataSourceNames().
Question is how to properly refactor ExecutionAdmin classes to correctly return these data sources (that are not technically data sources) so that getOrCreate works as does delete.
--
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
10 years, 10 months
[JBoss JIRA] (TEIIDDES-1765) StateInfo example does not succeed
by Van Halbert (JIRA)
Van Halbert created TEIIDDES-1765:
-------------------------------------
Summary: 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
10 years, 10 months
[JBoss JIRA] (TEIIDDES-1548) Add GUI handling for permission conditions
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1548?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1548:
----------------------------------------
Unlike "allow-languages" permissions, mask and condition permission properties need to get folded into the standard Data Role Permission class since they can apply to a column, just like CRUD, execute and alter.
Thinking need to manage these on separate tabs in the Data Role wizard, but if existing Permission defined for a column, go ahead and use it and not create a duplicate pointing to the same column.
> Add GUI handling for permission conditions
> ------------------------------------------
>
> Key: TEIIDDES-1548
> URL: https://issues.jboss.org/browse/TEIIDDES-1548
> Project: Teiid Designer
> Issue Type: Feature Request
> Reporter: Steven Hawkins
> Assignee: Barry LaFond
> Fix For: 8.2
>
>
> A common request is to implement row based security. Teiid has added the ability to define a permission condition for this purpose:
> <permission>
> <resource-name>...</resource-name>
> <condition>sql</condition>
> ...
> </permission>
> The sql should resolve against the resource specified, ideally designer would check that as well.
> See TEIID-2311 and the reference for how these conditions are applied.
> {code:title=vdb.xml snippet}
> <data-role name="base-role" any-authenticated="true">
> <description>Conditional access</description>
>
> <permission>
> <resource-name>modelName.tblName</resource-name>
> <condition constraint="false">column1=user()</condition>
> </permission>
>
> </data-role>
> {code}
--
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
10 years, 10 months