On 28 Jun 2013, at 08:47, Gonzalo Aguilar Delgado wrote: > Hi Christian, > > I managed to make it work with OpenAjax as you told me. It's great and works > perfectly. > > Do you know any reference about implementation details? I want to know more > about how wookie and rave communicates. I find this specially difficult
Hi Gonazalo, The Wookie OpenAjax feature is quite simple, and just looks for the availability of the OpenAjax Hub in Rave, and then provides the widget with access to it: http://svn.apache.org/viewvc/wookie/trunk/features/openajax/OpenAjaxClient.js?view=markup Wookie injects features into the Widget HTML, but doesn't interact directly with Rave at this level; in this case we know Rave implements OpenAjax so we just test for its availability (it would also work in any other platform using OpenAjax). The point at which Wookie and Rave interact is through the W3C Provider module in Rave; this calls the Wookie REST API to instantiate a Widget and generate the embed code. Here's the API Reference: http://wookie.apache.org/docs/api.html And here is the integration module within Rave: http://svn.apache.org/viewvc/rave/trunk/rave-providers/rave-w3c-provider/ HTH, S > > Thank you a lot! > > > El 28/06/13 07:02, Christian Fischer escribió: >> Hello, >> >>> What I don't understand is how Rave manages Wookie features? Because I >>> think that a feature that is declared must be inserted on top of the >>> general Rave header instead of the IFrame of the widget. Is this right or >>> not? >> >> Rave uses special OpenAjax Iframes for displaying OpenAjax enabled Widgets. >> Try reading the OpenAjax Hub Reference: >> http://www.openajax.org/member/wiki/OpenAjax_Hub_2.0_Specification >> >> Greets, >> Christian >
PGP.sig
Description: This is a digitally signed message part
