Hello Matthew,

thanks for your report. I've updated the svn repository.

Best regards,
Thierry Boileau

> Thanks again Thierry...
> That totally cleared up somethings that were getting in my way.
>
> As I started to take the objects and expanding some of the children objects, 
> I needed to use the .expand("") functions open to OData.
>
> According to the docs, this should now work in RC1.
>
> Using your generated code, I tried to expand the objects with:
> Query<RefFolderLocation>  query = 
> service.createRefFolderLocationQuery("/refFolderLocations(1)").expand("refURIType");
>
> The previous code does not load the child object's data(refURIType), although 
> it doesnt blow any errors.
>
> If we change the query to return a list:
> ("/refFolderLocations").expand("refURIType")
>
> We get
> Can't parse the content of 
> http://digital-furnace.com/OtherMeta/webdataservice.svc/refFolderLocations?$expand=refURIType
> java.io.IOException: Couldn't parse the source representation: 
> java.lang.NullPointerException
>
>
> This may be a bug?
>
> Matthew
>
>
>    
>> Hello Matthew,
>>
>> I send you a sample project that consumes your service using the classes
>> generated by the OData extension (actually the "RefForlderLocation"
>> entity). I was able to get and display the data.
>> I hope this will help you.
>>
>> Best regards,
>> Thierry Boileau
>>
>>      
>>> Thanks Thierry-
>>>
>>> I added             Engine.getInstance().getRegisteredClients().clear();
>>>             Engine.getInstance().getRegisteredClients().add(new 
>>> HttpClientHelper(new Client(Protocol.HTTP)));
>>>             Service myWCF = new 
>>> Service("http://digital-furnace.com/OtherMeta/webdataservice.svc/";);
>>>
>>>
>>> But no luck.  Same outcome.  No errors...but the objects are not getting 
>>> loaded.
>>>
>>> I do now get -
>>> [WARNING][org.restlet] No available client connector supports the required 
>>> protocols: 'HTTP' . Please add the JAR of a matching connector to your 
>>> classpath.
>>>
>>> But the correct JAR is in the classpath, as Protocol.HTTP is being resolved 
>>> from that JAR.
>>>
>>> Thanks
>>> Matthew
>>>
>>>
>>>        
>>>> Hello Matthew,
>>>>
>>>> I think your problem is due to the internal connector which does not
>>>> work with Android (see
>>>> http://restlet.tigris.org/issues/show_bug.cgi?id=304).
>>>> Can you try by adding the net extension (org.restlet.ext.net;jar) to the
>>>> classpath of your project with the following lines, for example in the
>>>> onCreate() method.
>>>>            Engine.getInstance().getRegisteredClients().clear();
>>>>            // Add the "net" client connector
>>>>            Engine.getInstance().getRegisteredClients().add(new
>>>> HttpClientHelper(new Client(Protocol.HTTP)));
>>>> Note that this is a workaround since the connectors are nor properly
>>>> discovered on the Android plate-form
>>>> (http://restlet.tigris.org/issues/show_bug.cgi?id=941).
>>>>
>>>> Regarding the log, we will provide a "bridge" between the classic Logger
>>>> and the android Log class.
>>>>
>>>> Best regards,
>>>> Thierry Boileau
>>>>
>>>>          
>>> ------------------------------------------------------
>>> http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2460828
>>>
>>>
>>>        
> ------------------------------------------------------
> http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2461210
>
>

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2463127

Reply via email to