[JBoss JIRA] (TEIIDDES-1156) Cache hint not being displayed after validation of Virtual Procedure in JBoss Developer Studio
by Johnathon Lee (Created) (JIRA)
Cache hint not being displayed after validation of Virtual Procedure in JBoss Developer Studio
----------------------------------------------------------------------------------------------
Key: TEIIDDES-1156
URL: https://issues.jboss.org/browse/TEIIDDES-1156
Project: Teiid Designer
Issue Type: Bug
Components: Teiid Integration
Affects Versions: 7.5, 7.4, 7.3, 7.2
Environment: JBoss Developer Studio 4.0
JBoss Developer Studio 4.1
Reporter: Johnathon Lee
/*+ cache */
CREATE VIRTUAL PROCEDURE
SELECT 'winning';
BEGIN
END
The cache hint is saved w/the Command Object even though it is not reflected in the display of the text after validation.
com.metamatrix.query.internal.ui.sqleditor.component.QueryDisplayComponent:313 & 314
The Command object on these lines has a member cacheHint, holding the reference to the cacheHint, this is ignored when the sqlText is set with the line:
this.sqlText = sqlDisplayNode.toDisplayString();
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (TEIIDDES-1213) Improve Web Service to Source Wizard
by Ted Jones (JIRA)
Ted Jones created TEIIDDES-1213:
-----------------------------------
Summary: Improve Web Service to Source Wizard
Key: TEIIDDES-1213
URL: https://issues.jboss.org/browse/TEIIDDES-1213
Project: Teiid Designer
Issue Type: Enhancement
Components: Import/Export
Affects Versions: 7.7
Reporter: Ted Jones
Assignee: Ted Jones
Fix For: 7.7.1
The Import WSDL into Source Model needs to work more like the XML File source wizard by allowing the user to select the columns they care about consuming (based on input and output schemas), creating a single "create" and "extract" procedure, and creating a virtual procedure to consume the "create" and "extract" procedures.
Note that multiple extract procedures should not be created in the case of nested complex data types. The fully qualified namespace should be added the single "extract" procedure.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] Created: (TEIIDDES-247) Salesforce Connector returns a blank error message box when running the getupdated procedure
by Debbie Steigner (JIRA)
Salesforce Connector returns a blank error message box when running the getupdated procedure
--------------------------------------------------------------------------------------------
Key: TEIIDDES-247
URL: https://jira.jboss.org/jira/browse/TEIIDDES-247
Project: Teiid Designer
Issue Type: Bug
Reporter: Debbie Steigner
Fix For: Future
If you execute the Salesforce getupdated procedure with a date range that returns an empty result set, instead of an empty result set you get an empty error message window and the following error in the log :
!STACK 1
ConnectorException: Status ERROR: com.metamatrix.core code=0 null
at com.metamatrix.connector.salesforce.connection.SalesforceConnection.getUpdated(SalesforceConnection.java:737)
at com.metamatrix.connector.salesforce.execution.GetUpdatedExecutionImpl.execute(GetUpdatedExecutionImpl.java:65)
at com.metamatrix.connector.salesforce.execution.ProcedureExecutionParentImpl.execute(ProcedureExecutionParentImpl.java:86)
at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.processNewRequest(ConnectorWorker.java:300)
at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.processBatchRequest(ConnectorWorker.java:165)
at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.process(ConnectorWorker.java:139)
at com.metamatrix.common.queue.QueueWorker.run(QueueWorker.java:64)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (TEIIDDES-1234) Generate WAR action processes with workspace models instead of model entries in the selected VDB
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-1234:
--------------------------------------
Summary: Generate WAR action processes with workspace models instead of model entries in the selected VDB
Key: TEIIDDES-1234
URL: https://issues.jboss.org/browse/TEIIDDES-1234
Project: Teiid Designer
Issue Type: Bug
Components: Web Services Support
Affects Versions: 7.7
Reporter: Barry LaFond
Assignee: Ted Jones
Priority: Critical
Fix For: 7.7
GenerateWarAction.selectionChanged() appears to be mixing apples and oranges. (See below)
I think the intent was to get the VdbModelEntry objects and cache up a list of WS Models for later use generating the proper procedure calls/URLs??
The colde below, however, is finding the corresponding ModelResource in the workspace for each entry, which could easily be "out of sync". Users would be unaware that the WAR they are creating might not be what they expect.
wsModelResources = new ArrayList<ModelResource>();
for (VdbModelEntry vdbModelEntry : modelEntrySet) {
final ModelResource modelResource = ModelerCore.getModelWorkspace().findModelResource(vdbModelEntry.getName());
if (ModelIdentifier.isWebServicesViewModel(modelResource)) {
enable = true;
// Add to our ArrayList of ModelResources. These
// will be used to generate the war artifacts.
wsModelResources.add(modelResource);
}
}
So I think we either not allow users to perform this action if the VDB was "out of sync" (probably not the best option)
or
Find another way to pass the model info necessary for the generator to perform whats needed.
Note that in VdbEditor class there is an example of creating a "Temporary" EMF model container in order to interrogate the models. So I believe it should be possible.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months