Asier schrieb: > El 06/04/2010 13:36, Torsten Schoenebaum escribió: > >> You don't have to use the participant registration method of RuoteKit at >> all. If you like to register participants dynamically, call the engine's >> registration method for yourself and don't use rk's convenience wrapper >> (the call should be something like >> RuoteKit.engine.register_participant participant_name, >> participant_class_or_instance, additional_args >> ). >> >> RuoteKit is just a wrapper to Ruote, it's perfectly well to use Ruote's >> methods directly. RuoteKit's power lies then therein that it provides >> you with a singleton method to access the engine (via RuoteKit.engine). > > Yes, but I think that will only work if I'm developing with Ruby and > have access to ruote internals, but if I'm working with an external > application (c#, java) I can't "interface" with Ruby, so there's the > need for ruote-kit and it's REST interface.
It should be really easy to build your own participant controller in a rk fork which takes care of participant registration. As John wrote: It depends on what you want to do. Did you consider using a catchall participant? Yours, Torsten -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en To unsubscribe, reply using "remove me" as the subject.
