>-----Original Message-----
>From: Marlon Pierce [mailto:[email protected]]
>Sent: Thursday, September 08, 2011 3:25 PM
>To: [email protected]
>Subject: Re: people.create, update, and delete not implemented in rave-
>shindig?
>
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>This is a limitation the Shindig API for PersonService
>(org.apache.shindig.social.opensocial.spi.PersonService). Matt
>implemented the API's get methods in DefaultPersonService, but to
>implement updatePerson requires a change to the Shindig interface.
I didn't see resolution on this issue. IMO, Rave-portal & rave-shindig should
share the same database instance for the demo application and in minor
deployments. Internally, we plan to do what we did with OSEC & Rave, which is
to define a common person service that both applications pull from.
>
>
>How should we proceed?
>
>
>Marlon
>
>
>On 9/8/11 2:32 PM, Marlon Pierce wrote:
>> We need a way to update the rave-shindig database from
>> rave-portal--for example, when a new user is created. I assume
>> this should be done through the OS API with rave-portal calling
>> shindig via REST or RPC API. However, it looks like person.create,
>> person.update, and person.delete are not implemented; person.get is
>> working ok.
>>
>> Assuming I'm not making a simple mistake, what do we need to do to
>> enable the additional person methods?
>>
>>
>> ----------------- Here is what I do: I have the following json
>>
>> { "method" : "people.get", "params" : { "userId" : "canonical" } }
>>
>> that I invoke with
>>
>> curl -H "Content-Type: application/json" -X POST -d
>> @json-person.txt http://localhost:8080/rpc
>>
>> This works ok. However, changing the method to person.create (or
>> update or delete) returns the following error:
>>
>> {"error":{"message":"notImplemented: The method people.create is
>> not implemented","code":501}}
>>
>> I realize I need to also create a authorization token and may have
>> an improperly formed JSON, but I assume these would throw
>> different errors if the service was implemented.
>>
>> I'm following
>> http://opensocial-resources.googlecode.com/svn/spec/2.0/Social-API-
>Server.xml#People-Service-Create
>>
>>
>>
>> Marlon
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
>Comment: GPGTools - http://gpgtools.org
>Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
>iQEcBAEBAgAGBQJOaRaaAAoJEEfVXEODPFID1m8H/jtNvbPngFRBUrGIyq9xLYo
>U
>kY7zpn0f+nkpuEBOalE4keDDHC77td20v9fFmS5JLhAfzvECN4bhDm8x5KDBZRgl
>sxc99PvJ+BeRZyVPtbx7E5pIAOoepJZGplUhyIvanIf2YZvh7CgDC03BhfqaeC0v
>cHnSknRZCilqti9nv+dBrKd9XUUnshR80wtFKm9cqtEHGaZYN82u+Ly+NYz2cizX
>OJk3WeXGRg+/kHjXPf203zBRaGgjf47VVFY0Qpj1E3MGGphvXhR1pzu97cId04g
>E
>lMP7krXUdMNWxdvbS9jx4KLn6z13ltnx6gKS9pI2xnoNIQpqFEdeuEyqCOeRJPQ
>=
>=DgG6
>-----END PGP SIGNATURE-----
