[JBoss JIRA] Created: (TEIIDDES-122) Add WSDL 2.0 Support to Designer for Data Services
by Ted Jones (JIRA)
Add WSDL 2.0 Support to Designer for Data Services
--------------------------------------------------
Key: TEIIDDES-122
URL: https://jira.jboss.org/jira/browse/TEIIDDES-122
Project: Teiid Designer
Issue Type: Feature Request
Affects Versions: 6.0.0
Reporter: Ted Jones
Fix For: 6.0.0
In order to support REST (see TEIID-417), we need to allow for the generation of WSDL 2.0 specific WSDL. We still need to allow for the generation of WSDL 1.1 since WSDL 2.0 is not widely supported by many tools.
There should be an option in the Designer to specify which version of the WSDL specification to use when generating the WSDL file. I suggest putting the option on the Web Services tab of the VDB, but I am open for other suggestions. Alternatively, we could add the WSDL using both specifications in separate WSDL files and then provide a different WSDL URL to get one or the other. This approach seems like overkill to me though and would have farther reaching ramifications.
Ideally this would be completed for Westport.
--
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, 4 months
[JBoss JIRA] Created: (TEIIDDES-126) Add a warning for the use of a model supports property
by Steven Hawkins (JIRA)
Add a warning for the use of a model supports property
------------------------------------------------------
Key: TEIIDDES-126
URL: https://jira.jboss.org/jira/browse/TEIIDDES-126
Project: Teiid Designer
Issue Type: Quality Risk
Components: Modeling
Affects Versions: 6.0.0
Reporter: Steven Hawkins
See TEIID-131. Model support properties that are simply overrides for connector binding properties are no longer checked by the Teiid runtime, rather TEIID-205 is used to control specific capabilities through the connector binding without requiring the creation of a custom capabilities class.
Usage of 'Set Criteria Max Size', Supports "Distinct', Supports "Join", Supports "Order By", Supports "Outer Join", and Supports "Where all" should generate a warning stating that the connector binding should be used instead.
--
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
13 years, 6 months