[Ctk-developers] data exchange in the DICOM Hosting implementation

Sascha Zelzer s.zelzer at dkfz-heidelberg.de
Thu Jun 9 12:06:38 UTC 2011


Yes, AFAIK the development of QtSOAP is "complete" in a sense that is 
does the things it was designed for (except for having some bugs, 
obviously...). I think Nokia just makes sure that it compiles with newer 
Qt versions.

Cheers,
Sascha

On 06/09/2011 09:49 AM, Benoit Bleuze wrote:
> Good news for all of us!
>
> Indeed Sascha, there are only 1-dimensional arrays in the specs.
> By the way do you know how active is the development of Qt Soap? I had the impression it was quite dormant, wasn't it?
>
> Cheers,
> Ben
>
>
> ----- Original Message -----
>> Hi Sascha,
>>
>> You can push that fix to your repo. The fix you provided fixed my
>> issue.
>>
>> Thanks for your help!
>>
>> Best,
>> Michael
>>
>> -----Original Message-----
>> From: Sascha Zelzer [mailto:s.zelzer at dkfz-heidelberg.de]
>> Sent: Wednesday, June 08, 2011 12:49 PM
>> To: Caylus, Michael (SCR US)
>> Cc: ctk-developers at commontk.org; Ljung, Patric (SCR US)
>> Subject: Re: [Ctk-developers] data exchange in the DICOM Hosting
>> implementation
>>
>> Hi Michael,
>>
>> it looks like the deserialization code of QtSoapArray is buggy. When
>> serializing a QtSoapArray instance to XML, it writes a position
>> attribute like "[3]", but when reading it in, this string is getting
>> converted to an integer which always leads to 0 (because the
>> conversion fails due to the brackets). Please try to replace line 1284
>> in qtsoap.cpp (located in your CTK superbuild build tree) with:
>>
>> pos = posattr.value().mid(1, posattr.value().size()-2).toInt();
>>
>> and make a build at the superbuild level. If that solves your problem
>> I will push that fix to our repo and update
>> http://www.commontk.org/index.php/Documentation/DicomApplicationHosting:DataExchangeDevelopment
>> with a comment. I am aware of the limitation that this will only allow
>> to deserialize one-dimensional arrays, but I think there is no
>> multi-dimensional use case in the DICOM AppHosting standard, so I
>> would refrain from writing support for it until we need it.
>>
>> Best,
>> Sascha
>>
>> On 06/08/2011 07:24 AM, Caylus, Michael (SCR US) wrote:
>>> Hi Sascha,
>>>
>>> I have been feeding the available data structure through multiple
>>> calls to the addToAvailableData(ctkDicomAppHosting::AvailableData&
>>> data,
>>>                           ctkDicomObjectLocatorCache*
>>>                           objectLocatorCache,
>>>                           const QString&  filename)
>>>
>>> function: one call per file found in my DICOM folder and then I send
>>> the notifyDataAvailable message only once.
>>>
>>> You should have got the SOAP messages on both the server and client
>>> side from my previous mail if not let me know I can send you the
>>> files again.
>>>
>>> I have also tried to send only the objectDescriptors array as
>>> suggested by Ben but I have observed the same issue.
>>>
>>> Best,
>>> Michael
>>>
>> _______________________________________________
>> Ctk-developers mailing list
>> Ctk-developers at commontk.org
>> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
> _______________________________________________
> Ctk-developers mailing list
> Ctk-developers at commontk.org
> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers




More information about the Ctk-developers mailing list