I have mixed feeling on this one. In principle I agree with Steve that as an integration
engine we need to make efforts to support legacy technologies. We also have to draw the
line somewhere.
I'm satisfied by the proposed solution. As you say we need ESB connectivity anyway,
and the ESB is a much richer env for dealing with XML.
That said, this will certainly get us some flack. There are a lot of bad non-WSI services
out there.
~jd
----- "Ramesh Reddy" <rareddy(a)redhat.com> wrote:
XML-Relational SOAP Connector (after the move to the CXF) it only
supports executing "Document-Literal" style web services.
XML-Source SOAP Connector is using Axis as the client library
supports
the "JAX-RPC" and as well as "Document-Literal" style web services.
As I am working to combine these both connectors into one JBoss WS
(native) and using only JAX-WS. Looks like JAX-WS only supports the
"doc-literal" style.
A question raised by SteveH is that since Teiid is an integration
engine
it should support connections to legacy technologies such as JAX-RPC
to
meet the user needs.
One option here is move the XML Connectors to the JAX-WS style, then
provide another connector that can be to JBoss ESB, where user can
choose to implement any kind of transport. Teiid team would like to
put
this on the road map irrespective of this particular need, however
the
question is if this will satisfy the needs of our users?
Thanks.
Ramesh..
_______________________________________________
teiid-dev mailing list
teiid-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/teiid-dev