[
https://issues.jboss.org/browse/TEIID-1241?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1241:
---------------------------------------
This could be bumped up to 7.7.1 based upon using the existing invoke method with the
action parameter as the port name to assist in situations where the WSDL specifies static
soap header information.
Create a WSDL based WS translator
---------------------------------
Key: TEIID-1241
URL:
https://issues.jboss.org/browse/TEIID-1241
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Affects Versions: 7.2
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.1
The current WS resource adapter was designed for low-level usage, which doesn't even
consult a WSDL. It would be good though to update the existing adapter/translator to
utilize a WSDL. The WSDL would be used to expose the operations through connector
metadata, so that the translator could create the corresponding procedures
model.service.port.binding.operation(arg...). Import options could be used to limit the
import to only particular services/ports.
The WSDL based approach would also allow for the CXF configuration to apply to more than
a single port and to more easily allow the policy definition for WS security.
Additional semantic support for RPC could be considered, but would need to use JAX-RPC
--
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