11 Jun
2007
11 Jun
'07
4:15 p.m.
I talked briefly to ludovic and he says we could reuse our GWT API.
We would need some wrappers in order to be able to call it directly
(for the serialization for example). That would allow us to focus on
having one AJAX API.
-Vincent
On Jun 11, 2007, at 3:35 PM, Vincent Massol wrote:
Hi,
I'm writing a treeview (using the yahoo treeview javascript api) to
display the list of all pages of a wiki and in order to have good
performances I need to call a server-side method for getting all
children pages of a given page (so that the nodes or the treeview
are loaded dynamically). In order to implement this I thus need a
new XWiki Action.
Now I think it would be good to generalize this common need. As we
add more Ajax to our UIs we'll need more and more calls from JS to
the server side.
I'm thus proposing a generic ExecuteXMLAction (or AjaxAction or
another name) that would do the following:
* Get the class, method and parameter to execute from the HTTP request
* Verify that the class is in the api package (to prevent security
issues)
* Call the method using introspection
* Return the result as XML using XStream (it generates
automatically XML from any java object)
Note: I'd need to define the format for sending the information in
the request. Not sure about which format to use.
WDYT?
Thanks
-Vincent
--
You receive this message as a subscriber of the xwiki-
dev(a)objectweb.org mailing list.
To unsubscribe: mailto:xwiki-dev-unsubscribe@objectweb.org
For general help: mailto:sympa@objectweb.org?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/
wws