org.embl.ebi.SoaplabServer.gowlab
Class RunPlugInDefaultImpl

java.lang.Object
  org.embl.ebi.SoaplabServer.gowlab.RunPlugInBaseImpl
      org.embl.ebi.SoaplabServer.gowlab.RunPlugInDefaultImpl

All Implemented Interfaces:

RunPlugIn

Direct Known Subclasses:

RunPlugInExternalImpl, RunPlugInXSLTImpl

public class RunPlugInDefaultImpl
extends RunPlugInBaseImpl

A default implementation of RunPlugIn interface.

It uses method GET or POST, depending on the properties given in the fetch(HTTPClient.HTTPConnection, HTTPClient.URI, HTTPClient.NVPair[], HTTPClient.NVPair[]) method.

Version:

$Id: RunPlugInDefaultImpl.java,v 1.1.1.1 2005/06/15 09:00:19 marsenger Exp $

Author:

Martin Senger

Field Summary

Fields inherited from interface org.embl.ebi.SoaplabServer.gowlab.RunPlugIn

DEBUG, METHOD_GET, METHOD_POST, PREFERRED_METHOD, RESULT_NAMES, SERVICE_NAME, XSLT_DIR, XSLT_FILE

Constructor Summary

RunPlugInDefaultImpl()

Method Summary

void	fetch(HTTPClient.HTTPConnection con, HTTPClient.URI supplierURI, HTTPClient.NVPair[] formData, HTTPClient.NVPair[] files) Send given data to a site using given connection, wait for an answer, and store results into given Result Manager.

Methods inherited from class org.embl.ebi.SoaplabServer.gowlab.RunPlugInBaseImpl

query2data, removeHtml, setEventManager, setProperties, setResultManager

Methods inherited from class java.lang.Object

equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

RunPlugInDefaultImpl

public RunPlugInDefaultImpl()

Method Detail

fetch

public void fetch(HTTPClient.HTTPConnection con,
                  HTTPClient.URI supplierURI,
                  HTTPClient.NVPair[] formData,
                  HTTPClient.NVPair[] files)

Send given data to a site using given connection, wait for an answer, and store results into given Result Manager.

This implementation does not use Event Manager, at all.

The following properties (if exist) are used:

• RunPlugIn.SERVICE_NAME
• RunPlugIn.RESULT_NAMES If this property does not exist, one result is sent to the Result Manager without any name (the manager itself guesses what name to use).

  If there is just one result name, an input stream tied to the response is sent to the Result Manager.

  If there are more results, this class buffers the whole response in the memory and then sets the same data for all given result names. Which obviously makes sense only if individual results have registered their own adapters, otherwise they all will be the same.

Specified by:

fetch in interface RunPlugIn

Specified by:

fetch in class RunPlugInBaseImpl

Parameters:

con - is an open connection to a site where to go

formData - are named values representing input data to be sent (usually they correspond to data sent from an HTML form if the page is accessed manually). Parameter may be null.

Sometimes it is expected to send a query string instead of name/value pairs of data. This is simulated by using 'formData' with only one element, whose 'name' part is null. The 'value' part is used as a query string.

files - represents files to be uploaded (together with the 'formData' they consitute full input data set). The data will be sent using multipart/form-data encoding. Each pair represents one file - the name refers to the 'name' attribute to be used in the header of the part, and the value is the actual filename (the file will be read and it's contents put in the body of that part). Parameter may be null.