[MOBY-dev] Calling moby-async category services

[Paul Gordon]

Hi Sylvie,

Yes, sorry about that.  I've moved the "handler != null" deeper into the 
function so that synchronous calls actually pickup the results too.  
It's in CVS now. Do you have a particular service of interest that I can 
use as a test case?

Regards,

Paul

Sylvie Huchet wrote:
> Bonjour Paul,
>
> Thanks for the update, but this is not enough.
> If the handler has to be null, the code of performAsyncSOAPRequest must be
> modified to get the data : The data is got back only if the following test :
> "if(newDataAvailable.size() > 0 && handler != null)" is true, which is never the
> case.
>
> Regards,
> Sylvie.
>
> Paul Gordon a écrit :
>   
>> Bonjour Sylvie,
>>
>> Thanks for pointing this out.  The handler is null as it's supposed to
>> be, but the lack of a StringBuffer was indeed the culprit.  This has
>> been fixed, and I'm adding a unit test for this (I'd always called
>> asynchronous services asynchronously( or sync ones either syncly or
>> asyncly), and so didn't catch this before)..
>>
>>
>>
>> Paul
>>
>> Sylvie Huchet wrote:
>>
>>     
>>> Hi Paul,
>>>
>>> It seems that MobyRequest does not handle both synchronous and
>>> asynchronous
>>> calls tranparently...
>>>
>>> The invokeService() method that can be called for asynchronous calls
>>> does not
>>> defines any handler to manage asynchronous calls. And thus the
>>> performAsyncSOAPRequest method does not return any result.
>>> In addition, the asynchronous part of the invokeService does not
>>> initialize the
>>> contentsXML which leads to a NullPointerException.
>>>
>>> Regards,
>>> Sylvie.
>>>
>>>
>>> Paul Gordon a écrit :
>>>  
>>>
>>>       
>>>> Hi Sylvie,
>>>>
>>>> The current class that implements asynchronous service calls is
>>>> MobyRequest (via AsyncClient).  You can find both synchronous and
>>>> asynchronous services by setting the Service category to the empty
>>>> string ("") before calling CentralImpl.  As Martin mentions below, the
>>>> mechanism currently used to run asynchronous services will change next
>>>> year (so there will probably be other ways to call async services
>>>> introduced), but the MobyRequest API will not need to change.
>>>> MobyRequest handles both synchronous and asynchronous calls
>>>> transparently.
>>>>
>>>> Regards,
>>>>
>>>> Paul
>>>>
>>>> Martin Senger wrote:
>>>>
>>>>    
>>>>
>>>>         
>>>>>> I'd like to know how asynchronous services (category moby-async)
>>>>>> can be
>>>>>> called
>>>>>> using the java API
>>>>>>             
>>>>>>             
>>>>> It is on the to-do list. A good opportunity to implement it will be the
>>>>> second week of February where several BioMoby developers meet at the
>>>>> Biohackaton in Japan. I hope to use this event to remove most of the
>>>>> items
>>>>> from my long-standing moby-to-do list. I am sorry for the delay.
>>>>>
>>>>> Martin
>>>>>
>>>>>         
>>>>>           
>>>> _______________________________________________
>>>> MOBY-dev mailing list
>>>> MOBY-dev at lists.open-bio.org
>>>> http://lists.open-bio.org/mailman/listinfo/moby-dev
>>>>
>>>>
>>>>     
>>>>         
>>>
>>>
>>>  
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> MOBY-dev mailing list
>>> MOBY-dev at lists.open-bio.org
>>> http://lists.open-bio.org/mailman/listinfo/moby-dev
>>>
>>>
>>> !DSPAM:60005,47977310109501808032233!
>>>   
>>>       
>> _______________________________________________
>> MOBY-dev mailing list
>> MOBY-dev at lists.open-bio.org
>> http://lists.open-bio.org/mailman/listinfo/moby-dev
>>
>>
>>     
>
>
> !DSPAM:60005,47984f74109501894423288!
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> MOBY-dev mailing list
> MOBY-dev at lists.open-bio.org
> http://lists.open-bio.org/mailman/listinfo/moby-dev
>
>
> !DSPAM:60005,47984f74109501894423288!
>