12 Jun
2009
12 Jun
'09
2:54 p.m.
Anca Paula Luca wrote:
On 06/12/2009 02:28 PM, Florin Ciubotaru wrote:
Right, there will be an additional pageId: String or page: Page parameter.
Hi,
XWiki has evolved a lot in the past year and new client apps were created.
Our current Xml-Rpc API is aligned to the Confluence 1.0 API
specification and hasn't been really enriched in a long time.
Since we have some distinct features like 'polyglot wiki' I propose to
create a new "xwiki2" method set to handle XWiki 2.0 method calls.
The new handler will be added to the Apache Xml-Rpc servlet properties file.
Proposed new xml-rpc methods(mostly needed for XEclipse, XOffice and XOO):
- parseFromHtml(String html, String syntax) : String
- render(String source, String syntaxId) : String
You'll need a context to do this right, the document for which the source must
be rendered (because you'll have relative references to images, links, etc in
the content, or macros which may require a complete context to be rendered
properly). Either you get it somehow on the server (which I don't see how can be
done) or you'll need to add it in the service interface.
Happy coding,
Anca
- cleanHtml(String dirtyHtml) : String
- add class ( http://jira.xwiki.org/jira/browse/XWIKI-3499 )
- getConfiguredSyntaxes
- getVirtualWikisNames
- getMacros, etc.
Proposed Xml-Rpc model extensions:
- Page
- syntaxId;
- ServerInfo/Wiki:
- isMultiWiki
- defaultSyntax
- encoding
WDYT?
Thanks,
Florin Ciubotaru
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs