Project

General

Profile

Feature #49

Create a SOAP endpoint on the server

Added by Paula Gearon over 15 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
Mulgara
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:

Description

Currently, the most common way for non-Java clients to connect to Mulgara is via SOAP.  This is done by wrapping the itql.jar in a SOAP endpoint, and calling that.  This gives a topology of:
<br/>

<br/>
Client &lt;---[SOAP]---&gt; Itql.jar &lt;---[RMI]---&gt; Mulgara
<br/>

<br/>
This double-network hop is horrible and inefficient.  It also has an unfortunate dependence on RMI.
<br/>

<br/>
Until we have a good HTTP solution (via [[NetKernel]]) it would be far preferable to allow the following:
<br/>

<br/>
Client &lt;---[SOAP]---&gt; Mulgara
<br/>

<br/>
This should not be too hard.  The main thing that the server needs is a means of converting iTQL queries from the client into Query objects used by the session.  Code already exists in [[ItqlInterpreter]] to do this, but it will to be decoupled from remote session creation (since it will now be done locally, and no finding of remote resources is necessary).
<br/>

<br/>
The other thing to do is:
<br/>
- Provide SOAP access to the Answer object.  This will help get it running, but is not suitable for real work (since SOAP calls would be needed to read every element of every line).
<br/>
- Convert small Answers into a DOM for returning.
<br/>
- Configure a streaming XML result set suitable to be parsed via SAX.  Hopefully this can be done?

No data to display

Also available in: Atom PDF