Re: Unsupported Attributes in Appointment

Hi,

please file a bug on the issue, it's best if you could add a small 
Python script which demonstrates the issue. If you don't know the 
proper component, just take the one you think matches best (I would say 
xmlrpcd in this case) and we'll reassign in case we think it belongs 
elsewhere.

regards,
   Helge

On 09.10.2003, at 16:20, Werner Schuster wrote:
> howdy,
>
> I stumbled about some odd behaviour of OG.o concerning some document
> fields that are described in the XmlRpc documentation;
> the concerned documents are Job and Appointment (there might be others,
> that I don't know about yet);
>
> The problem:
> a call to eg. appointment.update takes the Appointment document as 
> argument;
> but some of the fields documented in the XmlRpc doc. seem to be
> ignored  with the update call; if you send a document that contains
> these fields as an argument of the call, you don't
> get them back in the returned (updated) document;
> They cause "Unknown field" warnings when delete is called with a 
> document
> that contains these fields (the warnings are shown on the output of
> skyxmlrpcd);
>
> Another odd thing is the XmlRpc doc:
> the description of eg. the Appointment doc has a sample document (in
> Python) and a table describing the fields... but the fields that
> cause trouble are only in the table and not the sample code;
>
> The fields concerned for Appointment are: "type", "cycleEndDate",
> "aptType", and some more (for some info on the problem this causes in 
> JOGI
> see
> http://bugzilla.opengroupware.org/bugzilla/show_bug.cgi?id=269 , at 
> least
> I suppose that that bug is connected to this behaviour);
>
> I can file a bug on Bugzilla, though I am not sure which component this
> concerns (xmlrpcd, OG.o, ...);
-- 
OpenGroupware.org
http://www.opengroupware.org/

-- 
OpenGroupware.org XML-RPC
[email protected]
http://mail.opengroupware.org/mailman/listinfo/xmlrpc