[JBoss JIRA] (TEIIDDES-1251) Allow preview translators to have their properties changed
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1251?page=com.atlassian.jira.plu... ]
Steven Hawkins updated TEIIDDES-1251:
-------------------------------------
Summary: Allow preview translators to have their properties changed (was: Add "DefaultServiceMode" as optional Parameter in the WS translator)
Description: Previewing may not represent what the user wants or in some situations may not work, such as needed MESSAGE vs. PAYLOAD settings for the WS translator. The user should be able to tweak the preview to match their desired settings. (was: Currently "DefaultServiceMode" can only set on the WS translator extension property, which makes impossible for doing a preview from the Designer. In Designer you can only set translator overrides during VDB creation, however preview does not give any option for overrides. It quite possible in given service some calls may be done using MESSAGE, some with PAYLOAD. Adding a optional parmeter will solve these issues.)
Assignee: (was: Steven Hawkins)
> Allow preview translators to have their properties changed
> ----------------------------------------------------------
>
> Key: TEIIDDES-1251
> URL: https://issues.jboss.org/browse/TEIIDDES-1251
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Teiid Integration
> Affects Versions: 7.6
> Reporter: Ramesh Reddy
>
> Previewing may not represent what the user wants or in some situations may not work, such as needed MESSAGE vs. PAYLOAD settings for the WS translator. The user should be able to tweak the preview to match their desired settings.
--
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, 11 months
[JBoss JIRA] (TEIIDDES-1250) Need to improve the concept of how we're using and presenting the standard File and Web Service procedures
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-1250:
--------------------------------------
Summary: Need to improve the concept of how we're using and presenting the standard File and Web Service procedures
Key: TEIIDDES-1250
URL: https://issues.jboss.org/browse/TEIIDDES-1250
Project: Teiid Designer
Issue Type: Enhancement
Components: Modeling
Reporter: Barry LaFond
Priority: Critical
As we're developing more and more importers and model generators that utilize or require a source model containing getText(), getTextFiles(), invoke() or invokeHTTP(), it seems that we're spending a lot of time:
1) Re-coding the logic to generate them to utilize the "Source" or connection profile stored in them
2) Explaining to the user that this is "Required" and how/why it's happening.
The ONLY reason user-intervention is required is because currently, a Source model is needed as the carrier of the specific FILE or WSDL URL information. (Used to create "Data Source")
If this File/WSDL URL info was NOT included in these source models, then we could create a Built-in FileFunctions.xmi Source model that's delivered with the product and included in a VDB ANY time it's required.
To make this happen, we'd need another mechanism to persist the connection information and that might be the "View Model" that contains the SQL that contains the actual "File" or "URL" definition. This sort of makes sense.
I know our current "Preview Data" and "Create Data Source" framework only works with Source models, but if we could change this behavior we would save a LOT of pain and anguish for the user AND us developers in the future.
Currently this would simplify 3 different import wizards, remove a couple of Options in the "New > Teiid Metadata Model > Relational" wizard use case and remove a step or two from EACH cheat sheet or section in the documentation.
--
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, 11 months