From 460c52653ab0dcca6f19a4f492ed2c5e4e963ab0 Mon Sep 17 00:00:00 2001 From: toma Date: Wed, 25 Nov 2009 17:56:58 +0000 Subject: Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. BUG:215923 git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdepim@1054174 283d02a7-25f6-0310-bc7c-ecb5cbfe19da --- kresources/groupwise/soap/methods.xsd | 1429 +++++++++++++++++++++++++++++++++ 1 file changed, 1429 insertions(+) create mode 100644 kresources/groupwise/soap/methods.xsd (limited to 'kresources/groupwise/soap/methods.xsd') diff --git a/kresources/groupwise/soap/methods.xsd b/kresources/groupwise/soap/methods.xsd new file mode 100644 index 00000000..cfc24d85 --- /dev/null +++ b/kresources/groupwise/soap/methods.xsd @@ -0,0 +1,1429 @@ + + + + + + + + + + + + + + + + + + + + + + + + + If name is not present, the original name value from the + notification message will be used. + A container is requied for accepting a shared folder notification. + It is the container id of the parent folder under which the new + folder will be placed. + If container is not present, the shared folder will be put + under the Cabinet folder. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Forwarding a message is a two step process. + First you call the method with the id of the original item. + A new mail item is returned. + It has the orignal subject. + The caller is responsible to prepend "Fwd:" or what ever they + want to modify the original subject. + If the caller wants the original message body returned, they need + to supply message or message/RTF in the view. + It is up to the caller to modify the message body in any way. + When all of the changes to the returned mail item are complete, + the caller would then call sendRequest with the new mail item. + A linkInfo element is return in the mail item. That element needs + to be passed unchanged in the sendRequest. + If the caller wants to send the original item as an attachment to + the new mail item, the caller would pass the 'embed' element in the + forwardRequest. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + This work only for file attachments. + If you try to specify an embedded item, you will get an error. + If you specify offset = 0 and length = -1, + you will receive the whole attachment. + You can supply other values for offset and length to receive + a part of the attachment. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + container: The only valid container at this time is the GroupWise System Address book uid. + view: This is the view for the items that are returned. + + + + + + + + + + + + + + + + + + + + + + + The only valid container at this time is the GroupWise System Address book uid. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + This method will get a library, document or version object + depending on the arguments passed in. + versionNumber is a string. + It can take "current", "official" or a specific version number. + To get a version object, you must also supply a document number. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + This method provides a quicker access to mail items. + It does this by only access fields that are stored in the + database index. The fields in the index are: id, status, modified, + container, message type, categories, subject, orignalSubject, and + source. + The New list is the fastest access. + The Modified list is slower. + The All list is the slowest. + If you pass a startDate, the test is for any item that is newer + or equal to that date. + If you don't pass a container string. The query will be across + all folders. + If you don't pass a types list, the query will be for all message + types unless the container is the Calendar folder. In that case + the default will be "CalendarItem. "CalendarItem" is a special + case it represents Appointment, Note and Task. + You can select the source types you want to see. If you don't + specify a source, you will get received, draft and personal. + If you don't specify a view, the above fields will be returned. + If you specify other fields than the above fields, they will not + be returned. + You can restrict the number of items return by specifying a count. + All items will be returned if no count is given. + In the case of searching for items, the new startDate will be + returned for use in the next call to getQuickMessagesRequest. + The startDate is the time value before this read was performed. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + This method will link (copy) or move items into the container. + To do a link (copy) do not supply a from container. + To move item(s) from one container to another supply the from + container id. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + This method permanently deletes all items that were previously + marked for deletion (i.e. stored in the "Trash"). + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + If "start" or "end" is passed in "position", the value for "forward" + is ignored. + "start" will read from the start of the database going forward. + "end" will read from the end of the database going backward. + If you are making multiple calls to readCursorRequest, "position" + should either be "current" or not present after the first call. + + + + + + + + + + + + + + + + + + + + + + + + This method remove the custom field defintion not the field and + values within an item. + To delete custom defintions from personal address book entries, set + books = "1", else the definition will be deleted from mail items. + This method can take a long time to execute. + You can set doAsynchronous to have the custom field definition + removed in the background. + + + + + + + + + + + + + + + + + + + + + If the container is not specified then the item is + removed from all of the containers that it is linked + to and is stored in the "Trash". + If the container is specified then the item is only + removed from that specific container and it's link + is stored in the "Trash". + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The signature will be purged when remove + request completed. The missing id node + when it is not delete all signatures + indicates the removing of plain text signature + which resides in user's settings record. + + + + + + + + + + + + + + + + + + + + + Replying to a message is a two step process. + First you call the method with the id of the original item. + A new mail item is returned. + It has the orignal subject. + The caller is responsible to prepend "Re:" or what ever they + want to modify the original subject. + If the caller wants the original message body returned, they need + to supply message or message/RTF in the view. + It is up to the caller to modify the message body in any way. + When all of the changes to the returned mail item are complete, + the caller would then call sendRequest with the new mail item. + If the caller wants to reply to all recipeints of the original + item, the caller needs to pass recipients in the view. + If recipients is not in the view, the response will be addressed + to the original sender. + A linkInfo element is return in the mail item. That element needs + to be passed unchanged in the sendRequest. + + + + + + + + + + + + + + + + + + + + + If a recipient has opened or accepted a Calendar item, a notice + will be placed in the recipient's in-box when the item is + retracted. The notice can be affected by the following options: + + "comment": The comment will be included in the notice. + "retractCausedByResend": When TRUE, the notice will be suppressed + in lieu of the 'new' calendar item that will be delivered to + the recipient. + "retractingAllInstances": When TRUE, a single notice will be + placed in the recipient's in-box (instead of a notice for each auto-date + instance). + + If no retractType is specified, the default is recipientMailboxes. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The only version event types support are: + checkIn + checkOut + resetStatus + viewed + + + + + + + + + + + + + + + + + + + \ No newline at end of file -- cgit v1.2.3