6 Dec
2008
6 Dec
'08
2:46 p.m.
Ok. +1
Fabio Mancinelli wrote:
Artem Melentyev wrote:
You mean that storePage(page) should have the storePage(page, true)
behaviour by default, and storePage(page, false) is nonsense?
Actually storePage(page, false) which is equivalent to the current
storePage(page) is the default behavior that replaces the current content.
--
Artem Melentyev
Hi Fabio.
Fabio Mancinelli wrote:
Curently null values are not usable in XMLRPC so the previous one would
be (new Date(0), 0, 0, true).
And yes, it returns all.
Basically I directly feed numberOfResults and start parameters
to setLimit() and setOffset() methods of the Query object.
since the 1.7 release has been delayed I would
like to propose to add 3
methods to the XMLRPC API. These methods are the following:
/* Returns a list of all the changed pages starting from a given date */
public List<XWikiPageHistorySummary> getModifiedPagesHistory(
Date date,
Integer numberOfResults,
Integer start,
Boolean fromLatest)
should (null, 0, 0, true) return all?
/* These
are basically equivalent to original store functions, but if
checkVersion is true then a check of the current page version is done
before storing the page/object. This check handles the case in which a
page has been modified by somebody else after the last getPage or
getObject */
public XWikiPage storePage(XWikiPage page, Boolean checkVersion)
public XWikiObject storeObject(XWikiObject object, Boolean checkVersion)
What the
usecases for storePage(page, false) ?