Some questions about the API

"Werner Schuster" <[email protected]>
Newsgroups gmane.comp.cms.opengroupware.xmlrpc.devel
Message-ID <[email protected]>
howdy,

I am on the JOGI Team that is currently trying to write a Java API for
accessing OGo via XML-RPC;
There should be some release this or next week, but before that, we need
some information that we cannot gather from the supplied documentation;
We have been using the german SKYRIX XML-RPC documentation, but have found
it lacking in some areas. Our questions:

 - What is this "number" that is referred to in the doc some of the XMLRPC
calls (eg. account.getByNumber); is this supposed to be the ID, or is
this
something completely different?

 - ID:
  +does every document type have an ID? it seems like about all
parts of the XML-RPC have an *.fetchIds or *.getByID call, except for
project.*;
  + is this ID unique for each document or just for a document type; ie. can
2 documents have the same ID if they are eg. an Account and an Appointment?
  + what is the ID or what is it supposed to contain? Some XMLRPC sample
calls simply pass a number as argument, whereas others pass an URI that
contains the ID number;

 - Account:
   + does an Account have a "name" field? the example calls suggest that,
but it does not seem correct, or at least the description of the Account
document does not show it;
   + is there an easy way to get from an Account to a Person document?
the only possibility I can think of would be some query like
 'fetchPerson("login like xyz")' (where xyz is the login);
   + does every Account have an associated Person document?

 - Enterprise: what fields does this document contain? There is no
description of it in the documentation;

 - FetchSpecification: this name is used throughout the doc as a type for
argument; but for Account, Person, etc. it is basically a document with a
 "qualifier" and a "sortOrdering" field; BUT for Appointment (in its
fetch* functions) it is a document with at least a "startDate" and/or an
"endDate" field;
I have looked at the WebObjects documentation of some classes, and I found
the EOFetchSpecification class, which looks like the first kind (qualifier
and sortOrdering) fields);


OK, quite a lot of questions; but I hope someone of the OGo crew can
answer them;

murphee


-- 
OpenGroupware.org XML-RPC
[email protected]
http://mail.opengroupware.org/mailman/listinfo/xmlrpc
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.