Whether we can provide WebService protocol and the ftp protocol access node, this is the real follow Pipeline model.
Example:
<Node id="CALL_WEBSERVICES_0" type="CALL_WEBSERVICES" fieldMap="cloverField=webservicesArgs" />
Return type may be a need to increase the Object type, a developer may need to Object type conversion into other types of java.
eg.
(String)Object ; (Numeric)Object ; (Long)Object ; (Decimal)Object ; (Byte)Object ; (Integer)Object ; (Date)Object
eg.
DELIMITED_DATA_READER -> CALL_WEBSERVICES -> DELIMITED_DATA_WRITER
Example:
<Node id="CALL_WEBSERVICES_0" type="CALL_WEBSERVICES" fieldMap="cloverField=webservicesArgs" />
Return type may be a need to increase the Object type, a developer may need to Object type conversion into other types of java.
eg.
(String)Object ; (Numeric)Object ; (Long)Object ; (Decimal)Object ; (Byte)Object ; (Integer)Object ; (Date)Object
eg.
DELIMITED_DATA_READER -> CALL_WEBSERVICES -> DELIMITED_DATA_WRITER
-
Well, currently (Clover engine 2.3/2.4) does not have such component - CALL_WEBSERVICES.
It seems to me that you might go with XMLExtract or XMLXPathReader and modify it slightly - so it can read parameters from input, fire a HTTP GET request and then process&send out parsed result. -
Thank you for your response.
Hope to be in a higher version (Clover engine 2.4.1 or 2.5) can achieve such a visit webservice / ftp protocol access node, we can make up for the gaps in this area.
Please sign in to leave a comment.
Comments 2