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