GVSocialAdapter-Configuration - Revision history

G.dimaio at 08:12, 14 May 2014

2014-05-14T08:12:04Z

2013-01-08T17:21:55Z

2012-10-12T09:12:15Z

2012-10-08T10:23:06Z

‎Adapters Call

2012-10-08T10:01:55Z

2012-10-08T09:01:59Z

2012-09-21T13:08:43Z

2012-09-21T13:07:15Z

2012-09-21T13:04:37Z

2012-09-21T10:30:17Z

@@ Line 1: / Line 1: @@
 The Social adapter is an adapter which gives {{GVESB}} the ability to interact with social platforms. The platform integrated until now are:
-* [[TwitterAdapter]]
+* [[TwitterSocialAdapter]]
 The configuration is specified into the GVAdapter.xml, and the file has the following structure:

@@ Line 3: / Line 3: @@
 * [[TwitterAdapter]]
-The configuration is specified into the GVSocialAdapter-Configuration.xml, and the file has the following structure:
+The configuration is specified into the GVAdapter.xml, and the file has the following structure:
 <syntaxhighlight lang="xml">

@@ Line 77: / Line 77: @@
 </syntaxhighlight>
-SocialService is the root tag. It contains all the operation requested in a single adapter call. If you have to write a custom implementation of the adapter for a new social platform, you can still use this format replacing updateStatus with new-platform-operation-name, and specify all the attributes required in the leaf tags.
+SocialService is the root tag. It contains all the operation requested in a single adapter call. If you have to write a custom implementation of the adapter for a new social platform, you can still use this format replacing updateStatus with new-platform-operation-name, and specify all the attributes required in the leaf tags. Thus a generic call will look like:
 *Response:

@@ Line 76: / Line 76: @@
 </SocialService>
 </syntaxhighlight>
 *Response:
@@ Line 89: / Line 91: @@
 The tag '''updateStatus''' in the XML above is referred to an operation available in Twitter, more exactly is the one called to send a tweet. Each operation available for a Social platform has its own XML tag and parameters, and it is presented in [[{{VULCON}}]] allowing to define data transformation.

@@ Line 63: / Line 63: @@
 * the user's credentials are not spread, the application has its own tokens
 All the consumer tokens are specified into the configuration file for each account; the access tokens are defined by the [[GV Console]] and are stored into a properties file.
 The messages exchanged with the adapter have the following format:

← Older revision		Revision as of 09:01, 8 October 2012
Line 1:		Line 1:
−	The Social adapter is an adapter which gives {{GVESB}} the ability to interact with social platforms. The configuration is specified into the GVSocialAdapter-Configuration.xml, and the file has the following structure:	+	The Social adapter is an adapter which gives {{GVESB}} the ability to interact with social platforms. The platform integrated until now are:
		+
		+	* [[TwitterAdapter]]
		+
		+	The configuration is specified into the GVSocialAdapter-Configuration.xml, and the file has the following structure:

	<syntaxhighlight lang="xml">		<syntaxhighlight lang="xml">

@@ Line 58: / Line 58: @@
 * a user can revoke such permissions at any time
 * the user's credentials are not spread, the application has its own tokens
-All the consumer tokens are specified into the configuration file for each account; the access tokens are defined by the GVConsole and are stored into a properties file.
+All the consumer tokens are specified into the configuration file for each account; the access tokens are defined by the [[http://www.greenvulcano.com/gvwiki/index.php/GV_Console GV Console]] and are stored into a properties file.
 The messages exchanged with the adapter have the following format:

@@ Line 7: / Line 7: @@
                               social="twitter" type="social-adapter">
              <Accounts>
-                 <Account name="ACCOUNT_NAME" consumer_key="..." consumer_secret="..." oauth_access_token="..." oauth_access_token_secret="..."	twitteruserid="..."/>
+                 <Account name="ACCOUNT_NAME" consumer_key="..." consumer_secret="..." twitteruserid="..."/>
                  ...
              </Accounts>
@@ Line 39: / Line 39: @@
 |-
 | Account consumer_secret || OAuth parameter
 |-
 | Account twitteruserid || user id on the social platform
@@ Line 62: / Line 58: @@
 * a user can revoke such permissions at any time
 * the user's credentials are not spread, the application has its own tokens
-All the tokens are specified into the configuration file for each account.
+All the consumer tokens are specified into the configuration file for each account; the access tokens are defined by the GVConsole and are stored into a properties file.
 The messages exchanged with the adapter have the following format:

@@ Line 17: / Line 17: @@
 </syntaxhighlight>
-The XML above shows the configuration for [http://twitter.com Twitter] platform
+The XML above shows the configuration for [http://twitter.com Twitter] platform.
 The following table explains the configuration:
 {|class="gvtable"