Re: [teiid-dev] XML SOAP Connectors
On Wed, 2010-02-10 at 10:15 -0500, John Doyle wrote:
I've given this a lot of thought as well, perhaps from a
different direction than you. I hate to answer a question with a question, but here it
is. Are the dependencies really the issue? As you describe below, other JBoss projects
use 3rd party libraries as well.
Yes, generally we do not want to depend on some other technology if
there is a competing technology already offered in the host environment,
unless the other technology offers some feature that we depend upon.
This will reduce maintenance and support issues for Teiid.
I'm generally in favor of using JAX-WS (cxf) rather than Axis,
it's a newer and better spec in my opinion. But I don't know that the change is
worth the effort. I changed the XML_Relational connector to JAX-WS this because I was
unable to find a way to keep Axis from DOMing the response doc, which caused memory
issues.
Seems like JBossAS uses "native" in their 5.x line so far, CXF seems to
be their roadmap.
Bringing in the ESB makes a much more powerful and flexible solution
for federating with XML. It provides a better environment for manipulating XML that we
will ever produce. It's a solution we should recommend, but we still need a capable
XML/SOAP/REST story of our own if we going to call ourselves 'Data Federation'
IMHO.
We've talked about adding SQL/XML functions to the engine. If we
did this, I think we could get away with simple HTTP and JAX_WS connectors to source the
XML and rely upon the SQL/XML and XQuery functions in Teiid to manipulate it. If a user
wanted a stronger solution they could then use the ESB or other JBoss WS.
No
argument here. This is how we would want them to work in final state.
For this to happen, we need to remove the XML to relational based models
out of physical models and push them into virtual models and leave the
access as simple XML Source. Since this involves changes to the
Designer's importer and runtime, I would like to take this in through
multiple steps.
My main goal is make them work in JCA. Next, we will pull in ESB or
JAX-WS for access, then moving into SQL/XML functions and changes to
Designer. Will need figure out which version we do the work as time
permits for now.
Thanks
Ramesh..