You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@esme.apache.org by bu...@apache.org on 2011/06/27 15:55:31 UTC
svn commit: r791676 [1/8] - /websites/staging/esme/trunk/content/
Author: buildbot
Date: Mon Jun 27 13:55:28 2011
New Revision: 791676
Log:
Staging update by buildbot
Added:
websites/staging/esme/trunk/content/actions.cwiki
websites/staging/esme/trunk/content/actions.html
websites/staging/esme/trunk/content/actor-model.cwiki
websites/staging/esme/trunk/content/actor-model.html
websites/staging/esme/trunk/content/adobe-air.cwiki
websites/staging/esme/trunk/content/adobe-air.html
websites/staging/esme/trunk/content/akibot-use-case-description.cwiki
websites/staging/esme/trunk/content/akibot-use-case-description.html
websites/staging/esme/trunk/content/akibot-use-case.cwiki
websites/staging/esme/trunk/content/akibot-use-case.html
websites/staging/esme/trunk/content/ant-client.cwiki
websites/staging/esme/trunk/content/ant-client.html
websites/staging/esme/trunk/content/apache-esme-clients.cwiki
websites/staging/esme/trunk/content/apache-esme-clients.html
websites/staging/esme/trunk/content/apache-hudson.cwiki
websites/staging/esme/trunk/content/apache-hudson.html
websites/staging/esme/trunk/content/apache-james-(email-integration).cwiki
websites/staging/esme/trunk/content/api-2.0---design.cwiki
websites/staging/esme/trunk/content/api-2.0---design.html
websites/staging/esme/trunk/content/api.cwiki
websites/staging/esme/trunk/content/api.html
websites/staging/esme/trunk/content/architecture-patterns.cwiki
websites/staging/esme/trunk/content/architecture-patterns.html
websites/staging/esme/trunk/content/branding.cwiki
websites/staging/esme/trunk/content/branding.html
websites/staging/esme/trunk/content/build-apache-esme-from-subversion.cwiki
websites/staging/esme/trunk/content/build-apache-esme-from-subversion.html
websites/staging/esme/trunk/content/ce-installation-guide.cwiki
websites/staging/esme/trunk/content/ce-installation-guide.html
websites/staging/esme/trunk/content/collaboration-with-akibot.cwiki
websites/staging/esme/trunk/content/collaboration-with-akibot.html
websites/staging/esme/trunk/content/collaboration-with-ofbiz.cwiki
websites/staging/esme/trunk/content/collaboration-with-ofbiz.html
websites/staging/esme/trunk/content/collaboration-with-ubimic.cwiki
websites/staging/esme/trunk/content/collaboration-with-ubimic.html
websites/staging/esme/trunk/content/collaborations-with-other-organizations.cwiki
websites/staging/esme/trunk/content/collaborations-with-other-organizations.html
websites/staging/esme/trunk/content/database-scheme.cwiki
websites/staging/esme/trunk/content/database-scheme.html
websites/staging/esme/trunk/content/esme-as-chat-in-ofbiz.cwiki
websites/staging/esme/trunk/content/esme-as-chat-in-ofbiz.html
websites/staging/esme/trunk/content/esme-desktop-client-server-config.cwiki
websites/staging/esme/trunk/content/esme-desktop-client-server-config.html
websites/staging/esme/trunk/content/esme-installation-guides.cwiki
websites/staging/esme/trunk/content/esme-installation-guides.html
websites/staging/esme/trunk/content/esme-mailet-install-guide.cwiki
websites/staging/esme/trunk/content/esme-mailet-install-guide.html
websites/staging/esme/trunk/content/esme-privacy-policy.cwiki
websites/staging/esme/trunk/content/esme-privacy-policy.html
websites/staging/esme/trunk/content/existing-public-esme-installations.cwiki
websites/staging/esme/trunk/content/existing-public-esme-installations.html
websites/staging/esme/trunk/content/faq.cwiki
websites/staging/esme/trunk/content/faq.html
websites/staging/esme/trunk/content/getting-started.cwiki
websites/staging/esme/trunk/content/getting-started.html
websites/staging/esme/trunk/content/history.cwiki
websites/staging/esme/trunk/content/history.html
websites/staging/esme/trunk/content/human--vs.-machine-based-integration.cwiki
websites/staging/esme/trunk/content/human--vs.-machine-based-integration.html
websites/staging/esme/trunk/content/index.cwiki
websites/staging/esme/trunk/content/initial-comments-by-bill-fernandez.cwiki
websites/staging/esme/trunk/content/initial-comments-by-bill-fernandez.html
websites/staging/esme/trunk/content/integration-and-interfaces.cwiki
websites/staging/esme/trunk/content/integration-and-interfaces.html
websites/staging/esme/trunk/content/integration-with-thingamy.cwiki
websites/staging/esme/trunk/content/integration-with-thingamy.html
websites/staging/esme/trunk/content/java-servlet-container-installation-guide.cwiki
websites/staging/esme/trunk/content/java-servlet-container-installation-guide.html
websites/staging/esme/trunk/content/jmx-rest-api.cwiki
websites/staging/esme/trunk/content/jmx-rest-api.html
websites/staging/esme/trunk/content/jmx.cwiki
websites/staging/esme/trunk/content/jmx.html
websites/staging/esme/trunk/content/linux-(debian---ubuntu)-installation-guide.cwiki
websites/staging/esme/trunk/content/mac-os-x-10.6-installation-guide.cwiki
websites/staging/esme/trunk/content/mac-os-x-10.6-installation-guide.html
websites/staging/esme/trunk/content/message-deletion.cwiki
websites/staging/esme/trunk/content/message-deletion.html
websites/staging/esme/trunk/content/methods.cwiki
websites/staging/esme/trunk/content/methods.html
websites/staging/esme/trunk/content/original-api.cwiki
websites/staging/esme/trunk/content/original-api.html
websites/staging/esme/trunk/content/our-design-philosophy.cwiki
websites/staging/esme/trunk/content/our-design-philosophy.html
websites/staging/esme/trunk/content/our-history.cwiki
websites/staging/esme/trunk/content/our-history.html
websites/staging/esme/trunk/content/overall-design-discussions.cwiki
websites/staging/esme/trunk/content/overall-design-discussions.html
websites/staging/esme/trunk/content/pl-sql-client.cwiki
websites/staging/esme/trunk/content/pl-sql-client.html
websites/staging/esme/trunk/content/project-information.cwiki
websites/staging/esme/trunk/content/project-information.html
websites/staging/esme/trunk/content/pure-javascript-client.cwiki
websites/staging/esme/trunk/content/pure-javascript-client.html
websites/staging/esme/trunk/content/release-planning---best-practice-guide-2010.cwiki
websites/staging/esme/trunk/content/release-planning---best-practice-guide-2010.html
websites/staging/esme/trunk/content/restapi.cwiki
websites/staging/esme/trunk/content/restapi.html
websites/staging/esme/trunk/content/scala-action.cwiki
websites/staging/esme/trunk/content/scala-action.html
websites/staging/esme/trunk/content/server-configuration.cwiki
websites/staging/esme/trunk/content/server-configuration.html
websites/staging/esme/trunk/content/simple-use-case---ofbiz-sends-message-to-esme.cwiki
websites/staging/esme/trunk/content/simple-use-case---ofbiz-sends-message-to-esme.html
websites/staging/esme/trunk/content/statefulness-and-algorithms-for-social-networks-&-graphs.cwiki
websites/staging/esme/trunk/content/stax.cwiki
websites/staging/esme/trunk/content/stax.html
websites/staging/esme/trunk/content/streaming-api.cwiki
websites/staging/esme/trunk/content/streaming-api.html
websites/staging/esme/trunk/content/technical-architecture.cwiki
websites/staging/esme/trunk/content/technical-architecture.html
websites/staging/esme/trunk/content/twitter-api.cwiki
websites/staging/esme/trunk/content/twitter-api.html
websites/staging/esme/trunk/content/use-case---posting-from-sap-back-end.cwiki
websites/staging/esme/trunk/content/use-case---posting-from-sap-back-end.html
websites/staging/esme/trunk/content/vba.cwiki
websites/staging/esme/trunk/content/vba.html
websites/staging/esme/trunk/content/web-client.cwiki
websites/staging/esme/trunk/content/web-client.html
websites/staging/esme/trunk/content/web-ui-help.cwiki
websites/staging/esme/trunk/content/web-ui-help.html
websites/staging/esme/trunk/content/windows-vista-installation-guide.cwiki
websites/staging/esme/trunk/content/windows-vista-installation-guide.html
websites/staging/esme/trunk/content/windows-xp-installation-guide-(revision-885445).cwiki
websites/staging/esme/trunk/content/yql.cwiki
websites/staging/esme/trunk/content/yql.html
websites/staging/esme/trunk/content/zoho-creator.cwiki
websites/staging/esme/trunk/content/zoho-creator.html
Added: websites/staging/esme/trunk/content/actions.cwiki
==============================================================================
--- websites/staging/esme/trunk/content/actions.cwiki (added)
+++ websites/staging/esme/trunk/content/actions.cwiki Mon Jun 27 13:55:28 2011
@@ -0,0 +1,64 @@
+h4. Filters (tests)
+
+|| Syntax || Description || Example || Note ||
+| @_username_ | Selects messages sent by a particular user | @rhirsch | |
+| any | Selects all messages regardless of their characteristics | any | |
+| /_regex_/ | Selects messages if body matches a regular expression | /exception/ | |
+| "_string_" | Selects messages if body contains the case insensitive string | "sales order" | |
+| \#_tag_ | Selects the messages containing the tag. | \#project gumbo | Note the tag could be in the message as a hash code or created by the user directly as a tag |
+| to = @_username_ | Selects the messages that were sent to a particular user | to = @rhirsch | |
+| to = (@_username1_, @_username2_) | Selects the messages that were sent to multiple users. | to = (@rhirsch, @m) | List should be comma separated |
+| to <> @_username_ | Selects the messages that were not sent to a particular user | to <> @rhirsch | |
+| not(_exp_) | Selects the messages in which the expression evaluates to false | not("sales order" ) | |
+| _exp1_ \| _exp2_ | Selects the messages in which either expression is true | "sales order" \| "profit" | |
+| _exp1_ & _exp2_ | Selects the messages in which both expressions are true | "sales order" & "profit" | |
+| _number_% | Returns messages based on the percentage. | 44% | For example, the 45% will be true 45% of the time. |
+
+h4. Hooks (messages generated on system events)
+
+|| Syntax || Description || Notes ||
+| login | Selects the messages generated on user login. | |
+| follow | Selects the messages generated when a user follows you. | %f expands to follower nickname |
+| unfollow | Selects the messages generated when a user unfollows you. | %f expands to ex-follower nickname |
+| profile | Selects the messages generated when your profile is changed. | |
+| every _number_ mins | Generates messages at regular intervals and selects them. | The message is not saved\- too noisy, plus two identical tests never refer to the same event |
+
+{info:title=User, followers' and public timelines}
+Messages generated by events can be used in the actions test expression, since the event cause is attached to them. Messages generated by events appear by default in the user's timeline, but not in follower's timeline. The message can be resent to followers using the existing *resend* action, or suppressed from user's own timeline by means of the *filter* action. Any and all saved messages appear in the public timeline (this could be addressed by these messages being private by default in the future). {info} \|
+
+h4. Actions (performances)
+
+|| Syntax || Description || Example || Note ||
+| filter | Filter the message out and don't put it in your mailbox | filter | |
+| resend | Resend the message to all your followers regardless of their characteristics | resend | It will only be put in your followers timeline if it is not already there. |
+| http:// _server_ | Does an HTTP(S) POST of the message on a server with certain headers set | [http://user:password@identi.ca/api/statuses/update.xml] \\
+status=%s | Enter HTTP POST data on a new line; %s expands to original message, %u expands to user nickname, %i expands to image URL, %w expands to user's full (mnemonic: _w_ hole) name (first + last) |
+| mailto: _email_ | Send the body of the message to the email recipient | {noformat}
+mailto:wille.coyote@acme.com
+{noformat} | For custom mails, enter mail text on a new line; same expansions apply as for HTTP POST |
+| atom: _url://_ \\
+rss: _url://_ | Posts the new entries from Atom/RSS feed | atom:[http://twitter.com/statuses/user_timeline/esmeproject.atom] | Bots can also post to Apache ESME, but polling from Apache ESME is more secure and robust |
+| scala | Interprets the text of a message as Scala code and returns back the result | action which interprets the text of a message as Scala \\
+code and returns back the result | Details [here |Scala Action] |
+
+h4. Examples for assembling tests and actions
+
+|| Test || Action || Description || Similar to ||
+| follow | mailto: _mail_ | Sends mail when followed by any user | Twitter sends messages on follow |
+| unfollow | mailto: _mail_ | Sends mail when unfollowed by a user | Qwitter helps track who is unfollowing you |
+| profile | http:// _server_ | Sends HTTP POST when the profile is changed | @chinposin on Twitter tracks your avatar change to chinposin.com |
+| every 5 mins | rss:[http://blog.esme.us/feed/rss] | Updates new posts from the ESME blog | twitterfeed posts your blog titles to Twitter |
+| login | resend | Notifies your followers when you log in | Yammer notifies when a user logs in for the first time |
+| \#twitter & @me | [http://user:password@twitter.com/statuses/update.xml] \\
+status=%s | Posts all messages tagged _\#twitter_ to Twitter | Identi.ca integrates with Twitter by reposting messages |
+| \#bot \| @bot | [http://localhost:8080/api/send_msg] \\
+token=XXX&message=%u said: %s | Reposts customized message to the same ESME instance, possibly with a different user's credentials | twitterbots helps you retweet automatically |
+
+{warning:title=Too permissive action tests}
+Be careful, tests for the actions might apply to more messages than you think. For example, the tag filter applies not only to your messages, but also ones from people you're following. In the action above which posts to Twitter, if you forget to restrict the author, you might flood the twitter timeline with messages you didn't intend to post. {warning} \|
+
+h4. Additional Links
+
+There are many lists of ad-hoc Twitter third-party tools, some of which might be assembled in ESME using actions.
+* [http://tweeternet.com/]
+* [http://www.squidoo.com/twitterextensions]
\ No newline at end of file
Added: websites/staging/esme/trunk/content/actions.html
==============================================================================
--- websites/staging/esme/trunk/content/actions.html (added)
+++ websites/staging/esme/trunk/content/actions.html Mon Jun 27 13:55:28 2011
@@ -0,0 +1,189 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/css/esme.css" rel="stylesheet" type="text/css">
+ <title>Apache ESME - Actions</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+ <link rel="icon" type="image/png" href="/images/esme-logo/stanbol-favicon.png"/>
+</head>
+
+<body>
+ <div id="navigation">
+ <img alt="Apache ESME" width="220" height="101" src="/images/esme-logo/esme-powerd.gif"/>
+ <h1 id="esme_links">ESME links</h1>
+<ul>
+<li><a href="/index.html">Home</a></li>
+<li><a href="/team.html">Project Team</a></li>
+<li><a href="/docs/buildfromSVN.html">Building ESME</a></li>
+<li><a href="/docs/faq.html">FAQ</a></li>
+<li><a href="/docs/actions.html">Actions</a></li>
+<li><a href="/docs/apis.html">APIs</a></li>
+<li><a href="/docs/clients.html">Clients</a></li>
+<li><a href="/docs/collaboration.html">Collaboration</a></li>
+<li><a href="/docs/install.html">Installation Guides</a></li>
+<li><a href="/docs/yql.html">YQL</a><br />
+</li>
+</ul>
+<h1 id="asf_links">ASF links</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <h1 class="title">Actions</h1>
+ <p><a name="Actions-Filters(tests)"></a></p>
+<h4 id="filters_tests">Filters (tests)</h4>
+<table>
+<tr><th> Syntax </th><th> Description </th><th> Example </th><th> Note </th></tr>
+<tr><td> @_username_ </td><td> Selects messages sent by a particular user </td><td> @rhirsch </td><td> </td></tr>
+<tr><td> any </td><td> Selects all messages regardless of their characteristics </td><td> any </td><td> </td></tr>
+<tr><td> /_regex_/ </td><td> Selects messages if body matches a regular expression </td><td>
+/exception/ </td><td> </td></tr>
+<tr><td> "_string_" </td><td> Selects messages if body contains the case insensitive
+string </td><td> "sales order" </td><td> </td></tr>
+<tr><td> \#_tag_ </td><td> Selects the messages containing the tag. </td><td> \#project gumbo </td><td>
+Note the tag could be in the message as a hash code or created by the user
+directly as a tag </td></tr>
+<tr><td> to = @_username_ </td><td> Selects the messages that were sent to a particular
+user </td><td> to = @rhirsch </td><td> </td></tr>
+<tr><td> to = (@_username1_, @_username2_) </td><td> Selects the messages that were sent
+to multiple users. </td><td> to = (@rhirsch, @m) </td><td> List should be comma separated </td></tr>
+<tr><td> to <> @_username_ </td><td> Selects the messages that were not sent to a
+particular user </td><td> to <> @rhirsch </td><td> </td></tr>
+<tr><td> not(_exp_) </td><td> Selects the messages in which the expression evaluates to
+false </td><td> not("sales order" ) </td><td> </td></tr>
+<tr><td> _exp1_ \</td><td> _exp2_ </td><td> Selects the messages in which either expression is
+true </td><td> "sales order" \</td><td> "profit" </td><td> </td></tr>
+<tr><td> _exp1_ & _exp2_ </td><td> Selects the messages in which both expressions are true
+</td><td> "sales order" & "profit" </td><td> </td></tr>
+<tr><td> _number_% </td><td> Returns messages based on the percentage. </td><td> 44% </td><td> For
+example, the 45% will be true 45% of the time. </td></tr>
+</table>
+
+<p><a name="Actions-Hooks(messagesgeneratedonsystemevents)"></a></p>
+<h4 id="hooks_messages_generated_on_system_events">Hooks (messages generated on system events)</h4>
+<table>
+<tr><th> Syntax </th><th> Description </th><th> Notes </th></tr>
+<tr><td> login </td><td> Selects the messages generated on user login. </td><td> </td></tr>
+<tr><td> follow </td><td> Selects the messages generated when a user follows you. </td><td> %f
+expands to follower nickname </td></tr>
+<tr><td> unfollow </td><td> Selects the messages generated when a user unfollows you. </td><td> %f
+expands to ex-follower nickname </td></tr>
+<tr><td> profile </td><td> Selects the messages generated when your profile is changed. </td><td>
+</td></tr>
+<tr><td> every _number_ mins </td><td> Generates messages at regular intervals and selects
+them. </td><td> The message is not saved\- too noisy, plus two identical tests
+never refer to the same event </td></tr>
+</table>
+
+<p>{info:title=User, followers' and public timelines}
+Messages generated by events can be used in the actions test expression,
+since the event cause is attached to them. Messages generated by events
+appear by default in the user's timeline, but not in follower's timeline.
+The message can be resent to followers using the existing <em>resend</em> action,
+or suppressed from user's own timeline by means of the <em>filter</em> action. Any
+and all saved messages appear in the public timeline (this could be
+addressed by these messages being private by default in the future). {info}
+|</p>
+<p><a name="Actions-Actions(performances)"></a></p>
+<h4 id="actions_performances">Actions (performances)</h4>
+<table>
+<tr><th> Syntax </th><th> Description </th><th> Example </th><th> Note </th></tr>
+<tr><td> filter </td><td> Filter the message out and don't put it in your mailbox </td><td> filter
+</td><td> </td></tr>
+<tr><td> resend </td><td> Resend the message to all your followers regardless of their
+characteristics </td><td> resend </td><td> It will only be put in your followers timeline
+if it is not already there. </td></tr>
+
+status=%s | Enter HTTP POST data on a new line; %s expands to original
+message, %u expands to user nickname, %i expands to image URL, %w expands
+to user's full (mnemonic: _w_ hole) name (first + last) |
+<tr><td> mailto: _email_ </td><td> Send the body of the message to the email recipient </td><td>
+{noformat}
+</tr>
+mailto:wille.coyote@acme.com
+
+| atom: _url://_ \\
+ rss: _url://_ | Posts the new entries from Atom/RSS feed | atom:[http://twitter.com/statuses/user_timeline/esmeproject.atom]
+ | Bots can also post to Apache ESME, but polling from Apache ESME is more
+secure and robust |
+ | scala | Interprets the text of a message as Scala code and returns back
+the result | action which interprets the text of a message as Scala \\
+ code and returns back the result | Details [here |Scala Action]
+ |
+
+h4. Examples for assembling tests and actions
+
+|| Test || Action || Description || Similar to ||
+ | follow | mailto: _mail_ | Sends mail when followed by any user | Twitter
+sends messages on follow |
+ | unfollow | mailto: _mail_ | Sends mail when unfollowed by a user |
+Qwitter helps track who is unfollowing you |
+ | profile | http:// _server_ | Sends HTTP POST when the profile is changed
+| @chinposin on Twitter tracks your avatar change to chinposin.com |
+ | every 5 mins | rss:[http://blog.esme.us/feed/rss]
+ | Updates new posts from the ESME blog | twitterfeed posts your blog
+titles to Twitter |
+ | login | resend | Notifies your followers when you log in | Yammer
+notifies when a user logs in for the first time |
+ | \#twitter & @me | [http://user:password@twitter.com/statuses/update.xml]
+ \\
+ status=%s | Posts all messages tagged _\#twitter_ to Twitter | Identi.ca
+integrates with Twitter by reposting messages |
+ | \#bot \| @bot | [http://localhost:8080/api/send_msg]
+ \\
+ token=XXX&message=%u said: %s | Reposts customized message to the same ESME
+instance, possibly with a different user's credentials | twitterbots helps
+you retweet automatically |
+
+{warning:title=Too permissive action tests}
+ Be careful, tests for the actions might apply to more messages than you
+think. For example, the tag filter applies not only to your messages, but
+also ones from people you're following. In the action above which posts to
+Twitter, if you forget to restrict the author, you might flood the twitter
+timeline with messages you didn't intend to post. {warning} \|
+
+h4. Additional Links
+
+There are many lists of ad-hoc Twitter third-party tools, some of which
+might be assembled in ESME using actions.
+ * [http://tweeternet.com/]
+ * [http://www.squidoo.com/twitterextensions]
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2010 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, ESME and the Apache feather and ESME logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/esme/trunk/content/actor-model.cwiki
==============================================================================
--- websites/staging/esme/trunk/content/actor-model.cwiki (added)
+++ websites/staging/esme/trunk/content/actor-model.cwiki Mon Jun 27 13:55:28 2011
@@ -0,0 +1,2 @@
+ESME Actor Model
+{gliffy:name=ESME Actor Model|space=ESME|page=Actor Model|pageid=12321096|align=left|size=L}
\ No newline at end of file
Added: websites/staging/esme/trunk/content/actor-model.html
==============================================================================
--- websites/staging/esme/trunk/content/actor-model.html (added)
+++ websites/staging/esme/trunk/content/actor-model.html Mon Jun 27 13:55:28 2011
@@ -0,0 +1,74 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/css/esme.css" rel="stylesheet" type="text/css">
+ <title>Apache ESME - Actor Model</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+ <link rel="icon" type="image/png" href="/images/esme-logo/stanbol-favicon.png"/>
+</head>
+
+<body>
+ <div id="navigation">
+ <img alt="Apache ESME" width="220" height="101" src="/images/esme-logo/esme-powerd.gif"/>
+ <h1 id="esme_links">ESME links</h1>
+<ul>
+<li><a href="/index.html">Home</a></li>
+<li><a href="/team.html">Project Team</a></li>
+<li><a href="/docs/buildfromSVN.html">Building ESME</a></li>
+<li><a href="/docs/faq.html">FAQ</a></li>
+<li><a href="/docs/actions.html">Actions</a></li>
+<li><a href="/docs/apis.html">APIs</a></li>
+<li><a href="/docs/clients.html">Clients</a></li>
+<li><a href="/docs/collaboration.html">Collaboration</a></li>
+<li><a href="/docs/install.html">Installation Guides</a></li>
+<li><a href="/docs/yql.html">YQL</a><br />
+</li>
+</ul>
+<h1 id="asf_links">ASF links</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <h1 class="title">Actor Model</h1>
+ <p>ESME Actor Model
+{gliffy:name=ESME Actor Model|space=ESME|page=Actor
+Model|pageid=12321096|align=left|size=L}</p>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2010 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, ESME and the Apache feather and ESME logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/esme/trunk/content/adobe-air.cwiki
==============================================================================
--- websites/staging/esme/trunk/content/adobe-air.cwiki (added)
+++ websites/staging/esme/trunk/content/adobe-air.cwiki Mon Jun 27 13:55:28 2011
@@ -0,0 +1,54 @@
+*Name*: Adobe Air Client
+*Description*: This client was one of the first clients to be developed for ESME
+
+*Status*: Alpha
+
+*Download:* You can [download the client |http://esmeproject.googlecode.com/files/ESMEDesktop_v0.012.air]from the ESME Google Group.
+
+h2. Screenshots
+!esme-desktop.jpg!
+
+h2. Code
+Geting started with ESME Air Client development: Please watch this 5 min screencast [http://screencast.com/t/DGKsxpJxN8]
+
+The [source code |http://code.google.com/p/esmeproject/source/browse/#svn/trunk/esme-air]is available on the ESME Google Code group.
+
+h2. Help
+Open
+h2. Details
+* The client requires that you use a token to access ESME
+
+h2. Supporting materials
+
+h4. Installation
+
+Download and Install the latest Adobe AIR runtime from [http://get.adobe.com/air/]
+Download the latest released version of ESMEDesktop.air from [http://code.google.com/p/esmeproject/downloads/list]
+Follow the installation wizard to Install
+
+h4. Configuration
+
+*How to configure the ESME server ESME Desktop connects to ..*
+
+By default ESME Desktop connects to the ESME instance running at [http://www.esme.us], but if you are running your own instance of the server, you will need to change the server that ESME Desktop connects to .. here's how ..
+
+This setting is stored in your application storage directory in a file called preferences.xml ... the application storage directory path varies based on your operating system and your username
+
+*MacOS:*
+
+/Users/username/Library/Preferences/ESMEDesktop.05D8320A56ED876B4DC203B7387C89522DDC092F.1/Local Store/preferences.xml The GUID in the path may vary.
+
+*Windows:*
+
+C:\Documents and Settings\username\Application Data\ESMEDesktop.05D8320A56ED876B4DC203B7387C89522DDC092F.1\Local Store\preferences.xml
+
+If the file does not exist create preferences.xml and drop in the following xml and save .. <preferences> <preference name="ESME_APISERVER" value="http://api.esme.us/esme/api/"/> <preference name="ESME_SERVER" value="http://www.esme.us/esme/"/> </preferences>
+If the file exists then edit the values to your server urls. The new setting will be picked up the next time you start ESME Desktop.
+
+ [How to configure the client if you are using a different ESME server|ESME Desktop Client Server Config]
+
+An example preferences file. The value for _token_ is from the Manage Tokens link, after you log in via the web. <preferences>
+ <preference name="ESME_APISERVER" value="http://api.esme.us/esme/api/"/>
+ <preference name="ESME_SERVER" value="http://www.esme.us/esme/"/>
+ <preference name="token" value="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"/>
+</preferences>
Added: websites/staging/esme/trunk/content/adobe-air.html
==============================================================================
--- websites/staging/esme/trunk/content/adobe-air.html (added)
+++ websites/staging/esme/trunk/content/adobe-air.html Mon Jun 27 13:55:28 2011
@@ -0,0 +1,72 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/css/esme.css" rel="stylesheet" type="text/css">
+ <title>Apache ESME - Adobe Air</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+ <link rel="icon" type="image/png" href="/images/esme-logo/stanbol-favicon.png"/>
+</head>
+
+<body>
+ <div id="navigation">
+ <img alt="Apache ESME" width="220" height="101" src="/images/esme-logo/esme-powerd.gif"/>
+ <h1 id="esme_links">ESME links</h1>
+<ul>
+<li><a href="/index.html">Home</a></li>
+<li><a href="/team.html">Project Team</a></li>
+<li><a href="/docs/buildfromSVN.html">Building ESME</a></li>
+<li><a href="/docs/faq.html">FAQ</a></li>
+<li><a href="/docs/actions.html">Actions</a></li>
+<li><a href="/docs/apis.html">APIs</a></li>
+<li><a href="/docs/clients.html">Clients</a></li>
+<li><a href="/docs/collaboration.html">Collaboration</a></li>
+<li><a href="/docs/install.html">Installation Guides</a></li>
+<li><a href="/docs/yql.html">YQL</a><br />
+</li>
+</ul>
+<h1 id="asf_links">ASF links</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <h1 class="title">Adobe Air</h1>
+
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2010 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, ESME and the Apache feather and ESME logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/esme/trunk/content/akibot-use-case-description.cwiki
==============================================================================
--- websites/staging/esme/trunk/content/akibot-use-case-description.cwiki (added)
+++ websites/staging/esme/trunk/content/akibot-use-case-description.cwiki Mon Jun 27 13:55:28 2011
@@ -0,0 +1,86 @@
+{section}
+
+{column:width=70%}
+
+h2. Use case
+
+_(Taken from esme-dev mailing list: still needs to be confirmed)_
+# One of the Purchasing employees posted this in the Purchasing micro-blog group: "@victoria I just ordered 3,000 more G70" (G70 is an item "Kidco fireplace gate"). to let his boss know that he ordered what they discussed some days ago.
+# Akibot picked up the conversation and understood that 3,000 G70 were ordered (through the contextual analyzer
+# Akibot inquired the purchasing history for G70 (through an ERP feed) and noticed that this was an unusual quantity (through the directive processor)
+# Akibot then called up another application that inquiries the price for G70 in Amazon and other online retailers (through the directive processor as well)
+# Akibot found that Toys'r'us is selling G70 cheaper (through the directive processor as well)
+# Since Purchasing just ordered more G70, and competitors are selling it cheaper, there will be a problem\!
+# Akibot posts back a message alerting the Sales group: "Purchasing just ordered 3,000 more G70. We're selling it at $194.99, the competition at $184.99 (Toysrus)"
+# Sales will contact Purchasing, and either they lower the price or cancel the purchase order
+
+This "reasoning" that Akibot has, is through directives. This use case above is one directive. Akibot comes with standard directives and you can add custom directives ("teach" him). These directives can be shared by other companies using Akibot, so the more companies use Akibot, the more Akibot learns...
+
+h2. Technical Description
+
+
+h2. !akibot_esme.jpg|thumbnail!
+
+# Messages are post in ESME
+# ESME sends message to Akibot via HTTP POST
+# Akibot acknowledges the message reception by responding the HTTP POST call with an XML response
+# Akibot store the message and processes it through its Contextual Analyzer (C>A) module
+# If necessary, Akibot makes inquiries the corresponding enterprise (ERP or Groupware) application via HTTP REQUEST
+# The enterprise application processes the inquiry
+# The enterprise application responds to the inquiry with an XML response
+# Akibot processes the enterprise application response with its Directive Processor (DP), which decides if any action is to be taken
+# If Akibot decides that an action needs to be taken (for now, just sending back a message to the microblog) it does so by sending the message via HTTP POST call to ESME
+# (Optional) ESME can send back an acknowledge to Akibot letting it know that the message was successfully received
+
+h5. Integration analysis: ESME Action
+
+
+Use ESME's existing action architecture to post to akibot via its HTTP POST interface.
+
+We can post to twitter via this mechanism so should also be able to post to you guys as well.
+
+For example,
+
+[http|http://user:password@identi.ca/api/statuses/update.xml][://user:password@identi.ca/api/statuses/update.xml|http://user:password@identi.ca/api/statuses/update.xml]
+_status=%s_
+
+The Akibot REST API to send messages has the following parameters:
+
+|| Name \\ || Description \\ || Type \\ || Optional \\ || Example \\ ||
+| Message | Message to be sent \\ | String \\ | | We're going to launch the Akibot campaign on 11/26/09 \\ |
+| Key | Application Key \\ | String \\ | | |
+| Message ID | Id of the message to send \\ | | | 1214 \\ |
+| Urgent | Whether message is urgent or not \\ | Number | | 0 |
+| Private | Whether message is private or not \\ | Number | | 0 |
+| Group ID \\ | ID of group involved \\ | Number | | 1413 |
+| User ID \\ | ID of user sending the message \\ | Number | | 1765 |
+| User Nick \\ | Nickname of user sending the message \\ | String \\ | | BobSmith |
+| Message timestamp | Timestamp of message to be sent \\ | Timestamp | | 2009-11-03 10:07:08 |
+
+
+
+
+We just have to map our parameters to these values.
+{column}
+
+{column:width=30%}
+
+h3. Iterations
+
+# Use existing akibot infrastructure and attempt to use ESME's action mechanism to post to akibot's REST API
+# Start changing akibot infrastructure (contextual analyzer, etc) to be more ESME-specific
+
+h3. Questions
+
+# What sort of back-end system are we talking about? Are you already using a system that we can re-use for initial tests?
+# We also have to agree on what sort of message contents (formats, etc.) will be used Are there special words (invoice, etc.) that are necessary. This is, of course, linked to what sort of back-end you guys are using.
+# What sort of rules are present in the DP? The obvious one would be to create an ESME message.
+# Regarding 10, we do respond with a XML response to those submitting messages via REST API
+# Do you want to use the old REST API or the new "Streaming API" (Ethan's baby :->)?
+# We just probably use a POST action as Ethan suggests as a first step
+# You are right about the messaging threads needing standardization (especially 2 and 9). Maybe you can look at my table in the wiki page and tell me about what the parameters mean and whether they are optional or not. We will have to map them to our fields.
+# We also have to think about user-ids. Do they need to be synchronized? Probably....
+
+{column}
+
+{section}
\ No newline at end of file
Added: websites/staging/esme/trunk/content/akibot-use-case-description.html
==============================================================================
--- websites/staging/esme/trunk/content/akibot-use-case-description.html (added)
+++ websites/staging/esme/trunk/content/akibot-use-case-description.html Mon Jun 27 13:55:28 2011
@@ -0,0 +1,170 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/css/esme.css" rel="stylesheet" type="text/css">
+ <title>Apache ESME - Akibot Use Case description</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+ <link rel="icon" type="image/png" href="/images/esme-logo/stanbol-favicon.png"/>
+</head>
+
+<body>
+ <div id="navigation">
+ <img alt="Apache ESME" width="220" height="101" src="/images/esme-logo/esme-powerd.gif"/>
+ <h1 id="esme_links">ESME links</h1>
+<ul>
+<li><a href="/index.html">Home</a></li>
+<li><a href="/team.html">Project Team</a></li>
+<li><a href="/docs/buildfromSVN.html">Building ESME</a></li>
+<li><a href="/docs/faq.html">FAQ</a></li>
+<li><a href="/docs/actions.html">Actions</a></li>
+<li><a href="/docs/apis.html">APIs</a></li>
+<li><a href="/docs/clients.html">Clients</a></li>
+<li><a href="/docs/collaboration.html">Collaboration</a></li>
+<li><a href="/docs/install.html">Installation Guides</a></li>
+<li><a href="/docs/yql.html">YQL</a><br />
+</li>
+</ul>
+<h1 id="asf_links">ASF links</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <h1 class="title">Akibot Use Case description</h1>
+ <p>{section}</p>
+<p>{column:width=70%}</p>
+<p><a name="AkibotUseCasedescription-Usecase"></a></p>
+<h2 id="use_case">Use case</h2>
+<p><em>(Taken from esme-dev mailing list: still needs to be confirmed)</em>
+1. One of the Purchasing employees posted this in the Purchasing
+micro-blog group: "@victoria I just ordered 3,000 more G70" (G70 is an item
+"Kidco fireplace gate"). to let his boss know that he ordered what they
+discussed some days ago.
+1. Akibot picked up the conversation and understood that 3,000 G70
+were ordered (through the contextual analyzer
+1. Akibot inquired the purchasing history for G70 (through an ERP feed) and
+noticed that this was an unusual quantity (through the directive processor)
+1. Akibot then called up another application that inquiries the price for
+G70 in Amazon and other online retailers (through the directive processor
+as well)
+1. Akibot found that Toys'r'us is selling G70 cheaper (through the directive
+processor as well)
+1. Since Purchasing just ordered more G70, and competitors are selling it
+cheaper, there will be a problem!
+1. Akibot posts back a message alerting the Sales group: "Purchasing
+just ordered 3,000 more G70. We're selling it at $194.99, the competition
+at $184.99 (Toysrus)"
+1. Sales will contact Purchasing, and either they lower the price or cancel
+the purchase order</p>
+<p>This "reasoning" that Akibot has, is through directives. This use case
+above is one directive. Akibot comes with standard directives and you can
+add custom directives ("teach" him). These directives can be shared by
+other companies using Akibot, so the more companies use Akibot, the more
+Akibot learns...</p>
+<p><a name="AkibotUseCasedescription-TechnicalDescription"></a></p>
+<h2 id="technical_description">Technical Description</h2>
+<p><a name="AkibotUseCasedescription-!akibot_esme.jpg|thumbnail!"></a></p>
+<h2 id="akibot_esmejpgthumbnail">!akibot_esme.jpg|thumbnail!</h2>
+<ol>
+<li>Messages are post in ESME</li>
+<li>ESME sends message to Akibot via HTTP POST</li>
+<li>Akibot acknowledges the message reception by responding the HTTP POST
+call with an XML response</li>
+<li>Akibot store the message and processes it through its Contextual Analyzer
+(C>A) module</li>
+<li>If necessary, Akibot makes inquiries the corresponding enterprise (ERP or
+Groupware) application via HTTP REQUEST</li>
+<li>The enterprise application processes the inquiry</li>
+<li>The enterprise application responds to the inquiry with an XML response</li>
+<li>Akibot processes the enterprise application response with its Directive
+Processor (DP), which decides if any action is to be taken</li>
+<li>If Akibot decides that an action needs to be taken (for now, just sending
+back a message to the microblog) it does so by sending the message via HTTP
+POST call to ESME</li>
+<li>(Optional) ESME can send back an acknowledge to Akibot letting it know
+that the message was successfully received</li>
+</ol>
+<p><a name="AkibotUseCasedescription-Integrationanalysis:ESMEAction"></a></p>
+<h5 id="integration_analysis_esme_action">Integration analysis: ESME Action</h5>
+<p>Use ESME's existing action architecture to post to akibot via its HTTP POST
+interface.</p>
+<p>We can post to twitter via this mechanism so should also be able to post to
+you guys as well.</p>
+<p>For example,</p>
+<p><a href="http://user:password@identi.ca/api/statuses/update.xml">http</a>
+[://user:password@identi.ca/api/statuses/update.xml|http://user:password@identi.ca/api/statuses/update.xml]
+<em>status=%s</em></p>
+<p>The Akibot REST API to send messages has the following parameters:</p>
+<p>We just have to map our parameters to these values.
+{column}</p>
+<p>{column:width=30%}</p>
+<p><a name="AkibotUseCasedescription-Iterations"></a></p>
+<h3 id="iterations">Iterations</h3>
+<ol>
+<li>Use existing akibot infrastructure and attempt to use ESME's action
+mechanism to post to akibot's REST API</li>
+<li>Start changing akibot infrastructure (contextual analyzer, etc) to be
+more ESME-specific</li>
+</ol>
+<p><a name="AkibotUseCasedescription-Questions"></a></p>
+<h3 id="questions">Questions</h3>
+<ol>
+<li>What sort of back-end system are we talking about? Are you already using
+a system that we can re-use for initial tests?</li>
+<li>We also have to agree on what sort of message contents (formats, etc.)
+will be used Are there special words (invoice, etc.) that are necessary.
+This is, of course, linked to what sort of back-end you guys are using.</li>
+<li>What sort of rules are present in the DP? The obvious one would be to
+create an ESME message.</li>
+<li>Regarding 10, we do respond with a XML response to those submitting
+messages via REST API</li>
+<li>Do you want to use the old REST API or the new "Streaming API" (Ethan's
+baby :->)?</li>
+<li>We just probably use a POST action as Ethan suggests as a first step</li>
+<li>You are right about the messaging threads needing standardization
+(especially 2 and 9). Maybe you can look at my table in the wiki page and
+tell me about what the parameters mean and whether they are optional or
+not. We will have to map them to our fields.</li>
+<li>We also have to think about user-ids. Do they need to be synchronized?
+Probably....</li>
+</ol>
+<p>{column}</p>
+<p>{section}</p>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2010 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, ESME and the Apache feather and ESME logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/esme/trunk/content/akibot-use-case.cwiki
==============================================================================
--- websites/staging/esme/trunk/content/akibot-use-case.cwiki (added)
+++ websites/staging/esme/trunk/content/akibot-use-case.cwiki Mon Jun 27 13:55:28 2011
@@ -0,0 +1,57 @@
+{section}
+
+{column:width=70%}
+
+h2. Use case
+
+_(Taken from esme-dev mailing list: still needs to be confirmed)_
+# One of the Purchasing employees posted this in the Purchasing micro-blog group: "@victoria I just ordered 3,000 more G70" (G70 is an item "Kidco fireplace gate"). to let his boss know that he ordered what they discussed some days ago.
+# Akibot picked up the conversation and understood that 3,000 G70 were ordered (through the contextual analyzer
+# Akibot inquired the purchasing history for G70 (through an ERP feed) and noticed that this was an unusual quantity (through the directive processor)
+# Akibot then called up another application that inquiries the price for G70 in Amazon and other online retailers (through the directive processor as well)
+# Akibot found that Toys'r'us is selling G70 cheaper (through the directive processor as well)
+# Since Purchasing just ordered more G70, and competitors are selling it cheaper, there will be a problem\!
+# Akibot posts back a message alerting the Sales group: "Purchasing just ordered 3,000 more G70. We're selling it at $194.99, the competition at $184.99 (Toysrus)"
+# Sales will contact Purchasing, and either they lower the price or cancel the purchase order
+
+This "reasoning" that Akibot has, is through directives. This use case above is one directive. Akibot comes with standard directives and you can add custom directives ("teach" him). These directives can be shared by other companies using Akibot, so the more companies use Akibot, the more Akibot learns...
+
+h2. Technical Description
+
+
+h2. !akibot_esme.jpg|thumbnail!
+
+# Messages are post in ESME
+# ESME sends message to Akibot via HTTP POST
+# Akibot acknowledges the message reception by responding the HTTP POST call with an XML response
+# Akibot store the message and processes it through its Contextual Analyzer (C>A) module
+# If necessary, Akibot makes inquiries the corresponding enterprise (ERP or Groupware) application via HTTP REQUEST
+# The enterprise application processes the inquiry
+# The enterprise application responds to the inquiry with an XML response
+# Akibot processes the enterprise application response with its Directive Processor (DP), which decides if any action is to be taken
+# If Akibot decides that an action needs to be taken (for now, just sending back a message to the microblog) it does so by sending the message via HTTP POST call to ESME
+# (Optional) ESME can send back an acknowledge to Akibot letting it know that the message was successfully received
+
+{column}
+
+{column:width=30%}
+
+h3. Iterations
+
+# Use existing akibot infrastructure and attempt to use ESME's action mechanism to post to akibot's REST API
+# Start changing akibot infrastructure (contextual analyzer, etc) to be more ESME-specific
+
+h3. Questions
+
+# What sort of back-end system are we talking about? Are you already using a system that we can re-use for initial tests?
+# We also have to agree on what sort of message contents (formats, etc.) will be used Are there special words (invoice, etc.) that are necessary. This is, of course, linked to what sort of back-end you guys are using.
+# What sort of rules are present in the DP? The obvious one would be to create an ESME message.
+# Regarding 10, we do respond with a XML response to those submitting messages via REST API
+# Do you want to use the old REST API or the new "Streaming API" (Ethan's baby :->)?
+# We just probably use a POST action as Ethan suggests as a first step
+# You are right about the messaging threads needing standardization (especially 2 and 9). Maybe you can look at my table in the wiki page and tell me about what the parameters mean and whether they are optional or not. We will have to map them to our fields.
+# We also have to think about user-ids. Do they need to be synchronized? Probably....
+Column two text goes here
+{column}
+
+{section}
\ No newline at end of file
Added: websites/staging/esme/trunk/content/akibot-use-case.html
==============================================================================
--- websites/staging/esme/trunk/content/akibot-use-case.html (added)
+++ websites/staging/esme/trunk/content/akibot-use-case.html Mon Jun 27 13:55:28 2011
@@ -0,0 +1,159 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/css/esme.css" rel="stylesheet" type="text/css">
+ <title>Apache ESME - Akibot Use Case</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+ <link rel="icon" type="image/png" href="/images/esme-logo/stanbol-favicon.png"/>
+</head>
+
+<body>
+ <div id="navigation">
+ <img alt="Apache ESME" width="220" height="101" src="/images/esme-logo/esme-powerd.gif"/>
+ <h1 id="esme_links">ESME links</h1>
+<ul>
+<li><a href="/index.html">Home</a></li>
+<li><a href="/team.html">Project Team</a></li>
+<li><a href="/docs/buildfromSVN.html">Building ESME</a></li>
+<li><a href="/docs/faq.html">FAQ</a></li>
+<li><a href="/docs/actions.html">Actions</a></li>
+<li><a href="/docs/apis.html">APIs</a></li>
+<li><a href="/docs/clients.html">Clients</a></li>
+<li><a href="/docs/collaboration.html">Collaboration</a></li>
+<li><a href="/docs/install.html">Installation Guides</a></li>
+<li><a href="/docs/yql.html">YQL</a><br />
+</li>
+</ul>
+<h1 id="asf_links">ASF links</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <h1 class="title">Akibot Use Case</h1>
+ <p>{section}</p>
+<p>{column:width=70%}</p>
+<p><a name="AkibotUseCase-Usecase"></a></p>
+<h2 id="use_case">Use case</h2>
+<p><em>(Taken from esme-dev mailing list: still needs to be confirmed)</em>
+1. One of the Purchasing employees posted this in the Purchasing
+micro-blog group: "@victoria I just ordered 3,000 more G70" (G70 is an item
+"Kidco fireplace gate"). to let his boss know that he ordered what they
+discussed some days ago.
+1. Akibot picked up the conversation and understood that 3,000 G70
+were ordered (through the contextual analyzer
+1. Akibot inquired the purchasing history for G70 (through an ERP feed) and
+noticed that this was an unusual quantity (through the directive processor)
+1. Akibot then called up another application that inquiries the price for
+G70 in Amazon and other online retailers (through the directive processor
+as well)
+1. Akibot found that Toys'r'us is selling G70 cheaper (through the directive
+processor as well)
+1. Since Purchasing just ordered more G70, and competitors are selling it
+cheaper, there will be a problem!
+1. Akibot posts back a message alerting the Sales group: "Purchasing
+just ordered 3,000 more G70. We're selling it at $194.99, the competition
+at $184.99 (Toysrus)"
+1. Sales will contact Purchasing, and either they lower the price or cancel
+the purchase order</p>
+<p>This "reasoning" that Akibot has, is through directives. This use case
+above is one directive. Akibot comes with standard directives and you can
+add custom directives ("teach" him). These directives can be shared by
+other companies using Akibot, so the more companies use Akibot, the more
+Akibot learns...</p>
+<p><a name="AkibotUseCase-TechnicalDescription"></a></p>
+<h2 id="technical_description">Technical Description</h2>
+<p><a name="AkibotUseCase-!akibot_esme.jpg|thumbnail!"></a></p>
+<h2 id="akibot_esmejpgthumbnail">!akibot_esme.jpg|thumbnail!</h2>
+<ol>
+<li>Messages are post in ESME</li>
+<li>ESME sends message to Akibot via HTTP POST</li>
+<li>Akibot acknowledges the message reception by responding the HTTP POST
+call with an XML response</li>
+<li>Akibot store the message and processes it through its Contextual Analyzer
+(C>A) module</li>
+<li>If necessary, Akibot makes inquiries the corresponding enterprise (ERP or
+Groupware) application via HTTP REQUEST</li>
+<li>The enterprise application processes the inquiry</li>
+<li>The enterprise application responds to the inquiry with an XML response</li>
+<li>Akibot processes the enterprise application response with its Directive
+Processor (DP), which decides if any action is to be taken</li>
+<li>If Akibot decides that an action needs to be taken (for now, just sending
+back a message to the microblog) it does so by sending the message via HTTP
+POST call to ESME</li>
+<li>(Optional) ESME can send back an acknowledge to Akibot letting it know
+that the message was successfully received</li>
+</ol>
+<p>{column}</p>
+<p>{column:width=30%}</p>
+<p><a name="AkibotUseCase-Iterations"></a></p>
+<h3 id="iterations">Iterations</h3>
+<ol>
+<li>Use existing akibot infrastructure and attempt to use ESME's action
+mechanism to post to akibot's REST API</li>
+<li>Start changing akibot infrastructure (contextual analyzer, etc) to be
+more ESME-specific</li>
+</ol>
+<p><a name="AkibotUseCase-Questions"></a></p>
+<h3 id="questions">Questions</h3>
+<ol>
+<li>What sort of back-end system are we talking about? Are you already using
+a system that we can re-use for initial tests?</li>
+<li>We also have to agree on what sort of message contents (formats, etc.)
+will be used Are there special words (invoice, etc.) that are necessary.
+This is, of course, linked to what sort of back-end you guys are using.</li>
+<li>What sort of rules are present in the DP? The obvious one would be to
+create an ESME message.</li>
+<li>Regarding 10, we do respond with a XML response to those submitting
+messages via REST API</li>
+<li>Do you want to use the old REST API or the new "Streaming API" (Ethan's
+baby :->)?</li>
+<li>We just probably use a POST action as Ethan suggests as a first step</li>
+<li>You are right about the messaging threads needing standardization
+(especially 2 and 9). Maybe you can look at my table in the wiki page and
+tell me about what the parameters mean and whether they are optional or
+not. We will have to map them to our fields.</li>
+<li>We also have to think about user-ids. Do they need to be synchronized?
+Probably....
+Column two text goes here
+{column}</li>
+</ol>
+<p>{section}</p>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2010 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, ESME and the Apache feather and ESME logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/esme/trunk/content/ant-client.cwiki
==============================================================================
--- websites/staging/esme/trunk/content/ant-client.cwiki (added)
+++ websites/staging/esme/trunk/content/ant-client.cwiki Mon Jun 27 13:55:28 2011
@@ -0,0 +1,123 @@
+We have an integration with [Apache Ant|http://ant.apache.org/] which is âa Java-based build toolâ. It is now possible to send messages to Apache ESME that describe the progress of your build steps. This is especially useful when Apache ESME is being in development projects where individual developers can be made aware of the status of various-build related actions. For example, a development team could be informed that a build is broken or if it is successful.
+
+h4. Setup
+
+# Install Apache Ant
+# Install Apache Maven
+# Download the Apache Commons packages ["Codec"|http://commons.apache.org/codec/] and [Logger|http://commons.apache.org/logging/download_logging.cgi]. We also need [Apache "Httpclient|http://hc.apache.org/] . Please note that we are currently using the legacy 3.1 version of the HTTP Client.
+# Check-out the ESME java client: \_[https://svn.apache.org/repos/asf/esme/trunk/esme-java-client\_|https://svn.apache.org/repos/asf/esme/trunk/esme-java-client_]
+# Perform a maven build in this directory with the following command "_mvn compile package \-Dmaven.test.skip=true_" . This will create a jar file "esme-rest-api-0.1.jar" in the target directory.
+# Create \_lib _directory and copy "rest-api-0.1-SNAPSHOT.jar", "commons-codec-1.2.jar", "commons-httpclient-3.1.jar" into this directory.
+# Create _src_ directory and copy the "EsmeAntTask.java" file to this directory
+# Change the build.xml file to point to the appropriate directories
+# Change the token in the "esme" target in the build.xml file to a correct token.
+# Change the proxy in the "esme" target in the build.xml file to a correct proxy.
+# call _ant dist esme_ to test the application
+
+h4. Build.xml
+{code:lang=xml}
+<project name="EsmeViaAnt" default="dist" basedir=".">
+ <!-- set global properties for this build -->
+ <property name="src" location="src"/>
+ <property name="build" location="build"/>
+ <property name="dist" location="dist"/>
+
+ <path id="project.class.path">
+ <pathelement path="./dist/lib/EsmeViaAnt.jar:./lib/esme-rest-api-0.1.jar:./lib/commons-codec-1.4.jar:./lib/commons-logging-1.1.1.jar:./lib/commons-httpclient-3.1.jar"/>
+ </path>
+
+
+ <target name="init">
+ <!-- Create the time stamp -->
+ <tstamp/>
+ <!-- Create the build directory structure used by compile -->
+ <mkdir dir="${build}"/>
+ </target>
+
+ <target name="compile" depends="init"
+ description="compile the source " >
+ <!-- Compile the java code from ${src} into ${build} -->
+ <javac srcdir="${src}" destdir="${build}">
+ <classpath refid="project.class.path"/>
+ </javac>
+ </target>
+
+ <target name="dist" depends="compile"
+ description="generate the distribution" >
+ <!-- Create the distribution directory -->
+ <mkdir dir="${dist}/lib"/>
+
+ <!-- Put everything in ${build} into the jar file -->
+ <jar jarfile="${dist}/lib/EsmeViaAnt.jar" basedir="${build}"/>
+ </target>
+
+ <target name="esme"
+ description="Send Esme" >
+ <java fork="true"
+ classname="EsmeAntTask">
+ <arg value="http://esmecloudserverapache.dickhirsch.staxapps.net/api"/>
+ <arg value="31EL0R0M15NTD2LSOS0BKC5Y0P5JOVAC"/>
+ <arg value="myproxy:81"/>
+ <arg value="A message from the ant build process"/>
+ <classpath>
+ <pathelement path="./dist/lib/EsmeViaAnt.jar:./lib/esme-rest-api-0.1.jar:./lib/commons-codec-1.4.jar:./lib/commons-logging-1.1.1.jar:./lib/commons-httpclient-3.1.jar"/>
+ </classpath>
+
+ </java>
+ </target>
+
+</project>
+{code}
+
+
+h4. EsmeAntTask java class
+{code}
+import org.apache.esme.api.EsmeRestApi;
+import org.apache.esme.model.Message;
+
+public class EsmeAntTask
+{
+
+public static void main (String[] args) {
+
+ String apiUrl;
+ String authToken;
+ String localProxy;
+ String message;
+ EsmeRestApi esme;
+
+ apiUrl = args[0];
+ authToken = args[1];
+ localProxy = args[2];
+ message = args[3];
+
+ try {
+
+ esme = new EsmeRestApi(apiUrl);
+
+ if ((localProxy != null) && !("".equals(localProxy)))
+ {
+ // Split proxyHost:port into two parts
+ String[] proxy = localProxy.split(":");
+ esme.setProxy(proxy[0], Integer.parseInt(proxy[1]));
+ }
+
+ esme.login(authToken);
+
+ Message esmeMsg = new Message();
+
+ esmeMsg.setBody(message);
+
+ String[] tags = new String[1];
+ tags[0] = "Ant Task";
+
+ esmeMsg.setTags(tags);
+
+ esmeMsg.setSource("Ant");
+
+ esme.sendMsg(esmeMsg);
+ }
+ catch (Exception e) {}
+ }
+}
+{code}
\ No newline at end of file
Added: websites/staging/esme/trunk/content/ant-client.html
==============================================================================
--- websites/staging/esme/trunk/content/ant-client.html (added)
+++ websites/staging/esme/trunk/content/ant-client.html Mon Jun 27 13:55:28 2011
@@ -0,0 +1,226 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/css/esme.css" rel="stylesheet" type="text/css">
+ <title>Apache ESME - Ant Client</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+ <link rel="icon" type="image/png" href="/images/esme-logo/stanbol-favicon.png"/>
+</head>
+
+<body>
+ <div id="navigation">
+ <img alt="Apache ESME" width="220" height="101" src="/images/esme-logo/esme-powerd.gif"/>
+ <h1 id="esme_links">ESME links</h1>
+<ul>
+<li><a href="/index.html">Home</a></li>
+<li><a href="/team.html">Project Team</a></li>
+<li><a href="/docs/buildfromSVN.html">Building ESME</a></li>
+<li><a href="/docs/faq.html">FAQ</a></li>
+<li><a href="/docs/actions.html">Actions</a></li>
+<li><a href="/docs/apis.html">APIs</a></li>
+<li><a href="/docs/clients.html">Clients</a></li>
+<li><a href="/docs/collaboration.html">Collaboration</a></li>
+<li><a href="/docs/install.html">Installation Guides</a></li>
+<li><a href="/docs/yql.html">YQL</a><br />
+</li>
+</ul>
+<h1 id="asf_links">ASF links</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <h1 class="title">Ant Client</h1>
+ <p>We have an integration with <a href="http://ant.apache.org/">Apache Ant</a>
+ which is âa Java-based build toolâ. It is now possible to send
+messages to Apache ESME that describe the progress of your build steps.
+This is especially useful when Apache ESME is being in development projects
+where individual developers can be made aware of the status of
+various-build related actions. For example, a development team could be
+informed that a build is broken or if it is successful.</p>
+<p><a name="AntClient-Setup"></a></p>
+<h4 id="setup">Setup</h4>
+<ol>
+<li>Install Apache Ant</li>
+<li>Install Apache Maven</li>
+<li>Download the Apache Commons packages <a href="http://commons.apache.org/codec/">"Codec"</a>
+ and [Logger|http://commons.apache.org/logging/download_logging.cgi]
+. We also need [Apache "Httpclient|http://hc.apache.org/] .
+Please note that we are currently using the legacy 3.1 version of the
+HTTP Client. </li>
+<li>Check-out the ESME java client: _<a href="https://svn.apache.org/repos/asf/esme/trunk/esme-java-client_">https://svn.apache.org/repos/asf/esme/trunk/esme-java-client_</a></li>
+<li>Perform a maven build in this directory with the following command "<em>mvn
+compile package -Dmaven.test.skip=true</em>" . This will create a jar file
+"esme-rest-api-0.1.jar" in the target directory. </li>
+<li>Create _lib _directory and copy "rest-api-0.1-SNAPSHOT.jar",
+"commons-codec-1.2.jar", "commons-httpclient-3.1.jar" into this
+directory. </li>
+<li>Create <em>src</em> directory and copy the "EsmeAntTask.java" file to this
+directory</li>
+<li>Change the build.xml file to point to the appropriate directories</li>
+<li>Change the token in the "esme" target in the build.xml file to a correct
+token.</li>
+<li>Change the proxy in the "esme" target in the build.xml file to a correct
+proxy.</li>
+<li>call <em>ant dist esme</em> to test the application</li>
+</ol>
+<p><a name="AntClient-Build.xml"></a></p>
+<h4 id="buildxml">Build.xml</h4>
+<p>{code:lang=xml}
+<project name="EsmeViaAnt" default="dist" basedir=".">
+ <!-- set global properties for this build -->
+ <property name="src" location="src"/>
+ <property name="build" location="build"/>
+ <property name="dist" location="dist"/></p>
+<div class="codehilite"><pre><span class="o"><</span><span class="n">path</span> <span class="n">id</span><span class="o">=</span><span class="s">"project.class.path"</span><span class="o">></span>
+<span class="o"><</span><span class="n">pathelement</span>
+</pre></div>
+
+
+<p>path="./dist/lib/EsmeViaAnt.jar:./lib/esme-rest-api-0.1.jar:./lib/commons-codec-1.4.jar:./lib/commons-logging-1.1.1.jar:./lib/commons-httpclient-3.1.jar"/>
+ </path></p>
+<p><target name="init">
+ <!-- Create the time stamp -->
+ <tstamp/>
+ <!-- Create the build directory structure used by compile -->
+ <mkdir dir="${build}"/>
+ </target></p>
+<p><target name="compile" depends="init"
+ description="compile the source " >
+ <!-- Compile the java code from ${src} into ${build} -->
+ <javac srcdir="${src}" destdir="${build}">
+ <classpath refid="project.class.path"/>
+ </javac>
+ </target></p>
+<p><target name="dist" depends="compile"
+ description="generate the distribution" >
+ <!-- Create the distribution directory -->
+ <mkdir dir="${dist}/lib"/></p>
+<div class="codehilite"><pre><span class="c"><!-- Put everything in </span><span class="cp">${</span><span class="n">build</span><span class="cp">}</span><span class="c"> into the jar file --></span>
+<span class="nt"><jar</span> <span class="na">jarfile=</span><span class="s">"</span><span class="cp">${</span><span class="n">dist</span><span class="cp">}</span><span class="s">/lib/EsmeViaAnt.jar"</span> <span class="na">basedir=</span><span class="s">"</span><span class="cp">${</span><span class="n">build</span><span class="cp">}</span><span class="s">"/</span><span class="nt">></span>
+</pre></div>
+
+
+</target>
+
+<p><target name="esme"
+ description="Send Esme" >
+ <java fork="true"
+ classname="EsmeAntTask">
+ <arg
+value="http://esmecloudserverapache.dickhirsch.staxapps.net/api"/>
+ <arg value="31EL0R0M15NTD2LSOS0BKC5Y0P5JOVAC"/>
+ <arg value="myproxy:81"/>
+ <arg value="A message from the ant build process"/>
+ <classpath>
+ <pathelement
+path="./dist/lib/EsmeViaAnt.jar:./lib/esme-rest-api-0.1.jar:./lib/commons-codec-1.4.jar:./lib/commons-logging-1.1.1.jar:./lib/commons-httpclient-3.1.jar"/>
+ </classpath></p>
+<div class="codehilite"><pre> <span class="sr"></java></span>
+</pre></div>
+
+
+</target>
+
+</project>
+
+<div class="codehilite"><pre><span class="n">h4</span><span class="o">.</span> <span class="n">EsmeAntTask</span> <span class="n">java</span> <span class="n">class</span>
+</pre></div>
+
+
+<p>import org.apache.esme.api.EsmeRestApi;
+import org.apache.esme.model.Message;</p>
+<p>public class EsmeAntTask
+{</p>
+<p>public static void main (String<a href=".html" />
+ args) {</p>
+<p>String apiUrl;
+ String authToken;
+ String localProxy;
+ String message;
+ EsmeRestApi esme;</p>
+<p>apiUrl = args<a href="0.html">0</a>
+;
+ authToken = args<a href="1.html">1</a>
+;
+ localProxy = args<a href="2.html">2</a>
+;
+ message = args<a href="3.html">3</a>
+;</p>
+<p>try {</p>
+<div class="codehilite"><pre> <span class="n">esme</span> <span class="o">=</span> <span class="k">new</span> <span class="n">EsmeRestApi</span><span class="p">(</span><span class="n">apiUrl</span><span class="p">);</span>
+
+ <span class="k">if</span> <span class="p">((</span><span class="n">localProxy</span> <span class="o">!=</span> <span class="n">null</span><span class="p">)</span> <span class="o">&&</span> <span class="o">!</span><span class="p">(</span><span class="s">""</span><span class="o">.</span><span class="n">equals</span><span class="p">(</span><span class="n">localProxy</span><span class="p">)))</span>
+ <span class="p">{</span>
+ <span class="sr">//</span> <span class="n">Split</span> <span class="n">proxyHost:port</span> <span class="n">into</span> <span class="n">two</span> <span class="n">parts</span>
+ <span class="n">String</span><span class="o">[]</span><span class="p">(</span><span class="o">.</span><span class="n">html</span><span class="p">)</span>
+</pre></div>
+
+
+<p>proxy = localProxy.split(":");
+ esme.setProxy(proxy<a href="0.html">0</a>
+, Integer.parseInt(proxy[1]));
+ }</p>
+<div class="codehilite"><pre> <span class="n">esme</span><span class="o">.</span><span class="n">login</span><span class="p">(</span><span class="n">authToken</span><span class="p">);</span>
+
+ <span class="n">Message</span> <span class="n">esmeMsg</span> <span class="o">=</span> <span class="k">new</span> <span class="n">Message</span><span class="p">();</span>
+
+ <span class="n">esmeMsg</span><span class="o">.</span><span class="n">setBody</span><span class="p">(</span><span class="n">message</span><span class="p">);</span>
+
+ <span class="n">String</span><span class="o">[]</span><span class="p">(</span><span class="o">.</span><span class="n">html</span><span class="p">)</span>
+</pre></div>
+
+
+<p>tags = new String[1];
+ tags<a href="0.html">0</a>
+ = "Ant Task";</p>
+<div class="codehilite"><pre> <span class="n">esmeMsg</span><span class="o">.</span><span class="n">setTags</span><span class="p">(</span><span class="n">tags</span><span class="p">);</span>
+
+ <span class="n">esmeMsg</span><span class="o">.</span><span class="n">setSource</span><span class="p">(</span><span class="s">"Ant"</span><span class="p">);</span>
+
+ <span class="n">esme</span><span class="o">.</span><span class="n">sendMsg</span><span class="p">(</span><span class="n">esmeMsg</span><span class="p">);</span>
+</pre></div>
+
+
+<p>}
+ catch (Exception e) {}
+ }
+}</p>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2010 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, ESME and the Apache feather and ESME logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/esme/trunk/content/apache-esme-clients.cwiki
==============================================================================
--- websites/staging/esme/trunk/content/apache-esme-clients.cwiki (added)
+++ websites/staging/esme/trunk/content/apache-esme-clients.cwiki Mon Jun 27 13:55:28 2011
@@ -0,0 +1,75 @@
+* h5. {color:#000000}[Web Client|Web Client]{color}
+
+
+
+h4.
+
+* h5. [ABAP Web Dynpro|http://code.google.com/p/esmeproject/source/browse/#svn/tags/teched08_vegas_demo_jam/esme-abap] (Google Code project)
+
+
+
+
+h4.
+
+* h5. [Adobe AIR|Adobe AIR]
+
+
+
+
+
+h4.
+
+* h5. [Ant Client|Ant Client]
+
+
+
+
+
+h4.
+
+* h5. [Apache James|Apache James (Email integration)] (Email integration)
+
+
+
+
+
+h4.
+
+* h5. [Java Client|http://svn.apache.org/viewvc/esme/trunk/esme-java-client/]
+
+
+
+
+
+h4.
+
+* h5. [PL SQL Client|PL SQL Client]
+
+
+
+
+
+h4.
+
+* h5. [Pure JavaScript Client|Pure JavaScript Client]
+
+
+
+
+
+h4.
+
+* h5. [VBA Client|VBA]
+
+
+
+
+
+h4.
+
+* h5. [Zoho Creator|Zoho Creator]
+
+h4.
+
+
+h4.
\ No newline at end of file
Added: websites/staging/esme/trunk/content/apache-esme-clients.html
==============================================================================
--- websites/staging/esme/trunk/content/apache-esme-clients.html (added)
+++ websites/staging/esme/trunk/content/apache-esme-clients.html Mon Jun 27 13:55:28 2011
@@ -0,0 +1,126 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/css/esme.css" rel="stylesheet" type="text/css">
+ <title>Apache ESME - Apache ESME Clients</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+ <link rel="icon" type="image/png" href="/images/esme-logo/stanbol-favicon.png"/>
+</head>
+
+<body>
+ <div id="navigation">
+ <img alt="Apache ESME" width="220" height="101" src="/images/esme-logo/esme-powerd.gif"/>
+ <h1 id="esme_links">ESME links</h1>
+<ul>
+<li><a href="/index.html">Home</a></li>
+<li><a href="/team.html">Project Team</a></li>
+<li><a href="/docs/buildfromSVN.html">Building ESME</a></li>
+<li><a href="/docs/faq.html">FAQ</a></li>
+<li><a href="/docs/actions.html">Actions</a></li>
+<li><a href="/docs/apis.html">APIs</a></li>
+<li><a href="/docs/clients.html">Clients</a></li>
+<li><a href="/docs/collaboration.html">Collaboration</a></li>
+<li><a href="/docs/install.html">Installation Guides</a></li>
+<li><a href="/docs/yql.html">YQL</a><br />
+</li>
+</ul>
+<h1 id="asf_links">ASF links</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <h1 class="title">Apache ESME Clients</h1>
+ <ul>
+<li>h5. {color:#000000}<a href="web-client.html">Web Client</a>
+{color}</li>
+</ul>
+<p><a name="ApacheESMEClients-"></a></p>
+<h4 id="" />
+<ul>
+<li>h5. <a href="http://code.google.com/p/esmeproject/source/browse/#svn/tags/teched08_vegas_demo_jam/esme-abap">ABAP Web Dynpro</a>
+ (Google Code project)</li>
+</ul>
+<p><a name="ApacheESMEClients-"></a></p>
+<h4 id="_1" />
+<ul>
+<li>h5. <a href="adobe-air.html">Adobe AIR</a></li>
+</ul>
+<p><a name="ApacheESMEClients-"></a></p>
+<h4 id="_2" />
+<ul>
+<li>h5. <a href="ant-client.html">Ant Client</a></li>
+</ul>
+<p><a name="ApacheESMEClients-"></a></p>
+<h4 id="_3" />
+<ul>
+<li>h5. <a href="apache-james-(email-integration).html">Apache James</a>
+ (Email integration)</li>
+</ul>
+<p><a name="ApacheESMEClients-"></a></p>
+<h4 id="_4" />
+<ul>
+<li>h5. <a href="http://svn.apache.org/viewvc/esme/trunk/esme-java-client/">Java Client</a></li>
+</ul>
+<p><a name="ApacheESMEClients-"></a></p>
+<h4 id="_5" />
+<ul>
+<li>h5. <a href="pl-sql-client.html">PL SQL Client</a></li>
+</ul>
+<p><a name="ApacheESMEClients-"></a></p>
+<h4 id="_6" />
+<ul>
+<li>h5. <a href="pure-javascript-client.html">Pure JavaScript Client</a></li>
+</ul>
+<p><a name="ApacheESMEClients-"></a></p>
+<h4 id="_7" />
+<ul>
+<li>h5. <a href="vba.html">VBA Client</a></li>
+</ul>
+<p><a name="ApacheESMEClients-"></a></p>
+<h4 id="_8" />
+<ul>
+<li>h5. <a href="zoho-creator.html">Zoho Creator</a></li>
+</ul>
+<p><a name="ApacheESMEClients-"></a></p>
+<h4 id="_9" />
+<p><a name="ApacheESMEClients-"></a></p>
+<h4 id="_10" />
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2010 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, ESME and the Apache feather and ESME logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/esme/trunk/content/apache-hudson.cwiki
==============================================================================
--- websites/staging/esme/trunk/content/apache-hudson.cwiki (added)
+++ websites/staging/esme/trunk/content/apache-hudson.cwiki Mon Jun 27 13:55:28 2011
@@ -0,0 +1,7 @@
+We are now using [Apache Hudson|https://hudson.apache.org/hudson/job/ESME/] for daily builds. Every day, our code base is extracted from the subversion-based code repository, built and tests performed. This allows us to make sure that we have code base that is viable and assists in our quality control measures. JIRA items that were built also receive comments describing the successful build.
+
+
+!Apache Hudson.jpg|border=1!
+
+
+If you want to keep track of our builds, here is the [RSS feed|https://hudson.apache.org/hudson/job/ESME/rssAll].
\ No newline at end of file
Added: websites/staging/esme/trunk/content/apache-hudson.html
==============================================================================
--- websites/staging/esme/trunk/content/apache-hudson.html (added)
+++ websites/staging/esme/trunk/content/apache-hudson.html Mon Jun 27 13:55:28 2011
@@ -0,0 +1,80 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/css/esme.css" rel="stylesheet" type="text/css">
+ <title>Apache ESME - Apache Hudson</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+ <link rel="icon" type="image/png" href="/images/esme-logo/stanbol-favicon.png"/>
+</head>
+
+<body>
+ <div id="navigation">
+ <img alt="Apache ESME" width="220" height="101" src="/images/esme-logo/esme-powerd.gif"/>
+ <h1 id="esme_links">ESME links</h1>
+<ul>
+<li><a href="/index.html">Home</a></li>
+<li><a href="/team.html">Project Team</a></li>
+<li><a href="/docs/buildfromSVN.html">Building ESME</a></li>
+<li><a href="/docs/faq.html">FAQ</a></li>
+<li><a href="/docs/actions.html">Actions</a></li>
+<li><a href="/docs/apis.html">APIs</a></li>
+<li><a href="/docs/clients.html">Clients</a></li>
+<li><a href="/docs/collaboration.html">Collaboration</a></li>
+<li><a href="/docs/install.html">Installation Guides</a></li>
+<li><a href="/docs/yql.html">YQL</a><br />
+</li>
+</ul>
+<h1 id="asf_links">ASF links</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <h1 class="title">Apache Hudson</h1>
+ <p>We are now using <a href="https://hudson.apache.org/hudson/job/ESME/">Apache Hudson</a>
+ for daily builds. Every day, our code base is extracted from the
+subversion-based code repository, built and tests performed. This allows us
+to make sure that we have code base that is viable and assists in our
+quality control measures. JIRA items that were built also receive comments
+describing the successful build.</p>
+<p>!Apache Hudson.jpg|border=1!</p>
+<p>If you want to keep track of our builds, here is the <a href="https://hudson.apache.org/hudson/job/ESME/rssAll">RSS feed</a>
+.</p>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2010 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, ESME and the Apache feather and ESME logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/esme/trunk/content/apache-james-(email-integration).cwiki
==============================================================================
--- websites/staging/esme/trunk/content/apache-james-(email-integration).cwiki (added)
+++ websites/staging/esme/trunk/content/apache-james-(email-integration).cwiki Mon Jun 27 13:55:28 2011
@@ -0,0 +1,5 @@
+Daniel Koller has created an Apache ESME Mailet as a plugin for the Open source Mail Server [Apache James|http://james.apache.org/server/] which allows users of an Apache ESME infrastructure (both humans and technical systems) to send email messages to an Apache ESME instance using their own identity. Messages sent through the mailet show up as personal messages from these end users, so people following you get them in the respective blogging timeline.
+
+The install guide is available on [Google Docs|https://docs.google.com/Doc?id=df96bz6v_18cw9vrcwr&pli=1].
+
+This new functionality is especially useful for integrating legacy applications into the Apaache ESME environment inasmuch as many such applications might not be able to integrate via the REST API but usually have the ability to send emails. Furthermore, an email interface also allows users to post Apache ESME messages with mobile devices.
\ No newline at end of file