svn commit: r1147629 - in /esme/site/trunk/content/docs/apis: api-2.0---design.mdtext jmx-rest-api.mdtext

[rh...@apache.org]

Author: rhirsch
Date: Sun Jul 17 14:31:11 2011
New Revision: 1147629

URL: http://svn.apache.org/viewvc?rev=1147629&view=rev
Log:
[ESME-351] Move Wiki to CMS

Modified:
    esme/site/trunk/content/docs/apis/api-2.0---design.mdtext
    esme/site/trunk/content/docs/apis/jmx-rest-api.mdtext

Modified: esme/site/trunk/content/docs/apis/api-2.0---design.mdtext
URL: http://svn.apache.org/viewvc/esme/site/trunk/content/docs/apis/api-2.0---design.mdtext?rev=1147629&r1=1147628&r2=1147629&view=diff
==============================================================================
--- esme/site/trunk/content/docs/apis/api-2.0---design.mdtext (original)
+++ esme/site/trunk/content/docs/apis/api-2.0---design.mdtext Sun Jul 17 14:31:11 2011
@@ -99,7 +99,7 @@ defining the simulation method for the e
 ## 
 
 
-*Note on the call: *[api2/user/messages](http://esmecloudserverapache.dickhirsch.staxapps.net/api2/user/messages?via=SAPRiver&tag=bob&message=User+')
+Note on the call: *[api2/user/messages](http://esmecloudserverapache.dickhirsch.staxapps.net/api2/user/messages?via=SAPRiver&tag=bob&message=User+')
 
 That call uses "tag", not "tags". Looking at the API2 code, the parameter
 name needs to be "tags". 

Modified: esme/site/trunk/content/docs/apis/jmx-rest-api.mdtext
URL: http://svn.apache.org/viewvc/esme/site/trunk/content/docs/apis/jmx-rest-api.mdtext?rev=1147629&r1=1147628&r2=1147629&view=diff
==============================================================================
--- esme/site/trunk/content/docs/apis/jmx-rest-api.mdtext (original)
+++ esme/site/trunk/content/docs/apis/jmx-rest-api.mdtext Sun Jul 17 14:31:11 2011
@@ -1,7 +1,6 @@
 Title: JMX REST API
 
 <a name="JMXRESTAPI-Currently,justaplaceholder."></a>
-## Currently, just a place holder.
 
 *The following text is copied directly from the mailing list.*
 
@@ -36,7 +35,7 @@ BadResponse.
     &nbsp;<Attrubute name="att2" value="val2" />
     </AttributeList>
 
-== SAMPLES ==
+## SAMPLES 
 
     GET /jmx/mbeans
     <esme_api operation="mbeans" success="true">
@@ -102,7 +101,9 @@ BadResponse.
     </MBeanInfo>
     </esme_api>
 
-=================
+
+### Notes
+
 There is no security on the api. This obviously should not stay like this
 and should only be accessable with an administrator account.
 I tested it with the Stats MBean and the java.util.Logging MBean and it is
@@ -113,11 +114,12 @@ are set when the app is originally loade
 esme is totally immutable after it is constructed. It is worth thinking
 about switching to a property api like Configgy which uses mutable data
 structures for properties.
+
 We could change in real time things like resent & links period, refresh
 intervals, analyzer settings like long query time, db connection pool sizes
 etc.
+
 I didn't enable sending serialized objects through the REST api because it
 seems like more trouble than it's worth. Besides that sort of JMX
 functionality is only useful between servers and this api is really just
-for
-the cloud environment like stax which doesn't allow you to bind to ports.
+for the cloud environment like stax which doesn't allow you to bind to ports.