WSDL 8.0.1 backward compatibility with GW 7

You can't put "sid" in any view unless you
work with the 8.0.1 schema, login to an
8.0.1 POA and login with "1.03"

I would not be able to fix any filtering problems
found in 7.0.x. I did note there were changes
to filtering put in after the base 7.0.3 release.
They would be in the latest 7.0.3 hot patch.

>>> On Wednesday, November 04, 2009 at 3:26 PM,
schneoka<schneoka@no-mx.forums.novell.com> wrote:

> The problems I reported in the thread from October 26 (new element sid
> in readCursorRequest) I got using the 7.0.x gwws.jar and the version
> string "1.0".
>
> Filter on custom fields really works with GW 7.0.2 but obviously not
> with 7.0.3
>
> Oskar
>
>
> Preston Stephenson;1883360 Wrote:
>> Are you saying if you use a 7.0.x gwws.jar file and
>> connect to a 8.0.1 POA and pass "1.0" in the <version>
>> element, that you have a problem?
>>
>> You can't use an 8.0.x gwws.jar file and connect
>> to a 7.0.x POA.
>>
>> You can't filter on custom fields in a 7.0.x POA.
>>
>> >>> On Wednesday, November 04, 2009 at 11:56 AM,
>> schneoka<schneoka@no‑mx.forums.novell.com> wrote:
>>
>> > Hi,
>> >
>> > the new gwws.jar seems to work now with GW 8.0.1
>> > But it seems to be no longer backward compatible with GW 7.
>> Connecting
>> > to a GW 7.0.2 POA I get the following error :
>> >
>> > Fehler beim Aufheben der Serialisierung: Fehler im
>> XML‑Leseprogramm:
>> > Unerwarteter Zeicheninhalt: "owner.postoffice1.de"
>> > at
>> >
>>
com.sun.xml.rpc.client.StreamingSender._handleRunt imeExceptionInSend(Streami

>>
>> > ngSender.java:331)
>> > at
>> >
>> com.sun.xml.rpc.client.StreamingSender._send(Strea mingSender.java:313)
>> > at
>> >
>>
com.novell.groupwise.ws.GroupWisePortType_Stub.get FolderListRequest(GroupWis

>>
>> > ePortType_Stub.java:1380)
>> >
>> >
>> > I assume that the problem is due to the changed owner scheme of
>> > SharedFolder / SharedBook.
>> > Here the SOAP trace :
>> >
>> > <gwt:folder
xmlns:xsi="http://www.w3.org/2001/XMLSchema‑instance"
>> > xsi:type="gwt:SharedFolder">
>> >
>>
<gwt:id>4AF1D523.coi.postoffice1.100.1386F69.1.D4D .1@34:4AF1D497.coi.postof

>> fic
>> > e1.100.1366973.1.146.1</gwt:id>
>> > <gwt:name>shfld_name</gwt:name>
>> > <gwt:modified>2009‑11‑04T18:46:07Z </gwt:modified>
>> > <gwt:parent>C.share.postoffice1.100.0.1.0.1@21</gwt:parent>
>> > <gwt:sequence>0</gwt:sequence>
>> > <gwt:acl>
>> > <gwt:entry>
>> > <gwt:displayName>owner</gwt:displayName>
>> > <gwt:email>owner.postoffice1.de</gwt:email>
>> >
<gwt:uuid>ACEB2300‑074C‑0000‑ 94A0‑88253CF1D88
E</gwt:uuid>
>> > <gwt:rights>
>> > <gwt:read>1</gwt:read>
>> > <gwt:add>1</gwt:add>
>> > </gwt:rights>
>> > </gwt:entry>
>> > </gwt:acl>
>> > <gwt:owner>owner.postoffice1.de</gwt:owner>
>> > <gwt:isSharedToMe>1</gwt:isSharedToMe>
>> > </gwt:folder>
>> >
>> > I have to use a TCP sniffer because the gwTrace flag seems not to
>> work,
>> > too.
>> >
>> > In the discussion from September 10th you suggest to use a version
>> > identifier different from "1.03" in the loginRequest if we don't
>> want
>> > the changes for the 8.0.1 schema
>> > That does not work because I always use a version id of 1.0 and was
>> > nevertheless forced to use the new gwws.jar for connecting to GW
>> 8.0.1
>> >
>> > We have to connect to GW 7 and GW 8 postoffices. How can we do that
>> > without using different WSDL implementations?
>> >
>> > Still another question about GW 7.0.3 : Are there any issues using
>> > filters? I get no items with GW 7.0.3 if I use complex FilterEntries
>> > (with a filter condition for a Custom property).
>> >
>> > Oskar
>
>
> ‑‑ schneoka
>
‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑†‘‑‑‑‑‑‑‑‑â
€‘‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑ ‑‑‑‑‑‑‑‑â€
‘‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑⠀‘‑‑‑‑
> schneoka's Profile: http://forums.novell.com/members/schneoka.html
> View this thread: WSDL 8.0.1 backward compatibility with GW 7