[teiid-dev] what should a translator-ws look like?

Steven Hawkins shawkins at redhat.com
Mon Jun 7 16:15:13 EDT 2010


Hello all,

Based upon the features of the translator-xml, we need a comparable translator-ws that has a job of simply invoking a service and returning a document (which can then be processed with xmltable or any other mechanism).  I was thinking of exposing the procedure: 

XML invoke(XML request, String endpoint, String soapaction) - both endpoint and soapaction default to null and the result is available as the return parameter.
  
With the  HTTP mode:

-with parameter invocation the request document is expected to be in the format <params><para_name>value</para_name><param_name1>...</params>.  The simplest way to form such a doc is with xmlforest - xmlelement(params, xmlforest(value as param_name, value1 as param_name1 ...)) 

-Path info will be taken from endpoint if it's specified and will be expected to be a relative path.

-soapaction would not be used.

Basic usage would then be:

call ws-model.invoke(request = value)

Other considerations:

We may also want to add system function(s) with nearly the same approach to allow for ad hoc, non-JCA based service calls.
We may want to add more explicit calling functionality for http to support rest.

Steve


More information about the teiid-dev mailing list