Hi ant, Wink and JSON technologies can be used to for interaction between the back end runtime composites and the management console. For an example when all the ProviderFactoryExtensionPoints are needed to be shown on the console, an object containing all information is sent, and Wink converts it to a JSON message. The console can read the JSON message and display the information.
It can be used inthe other way roud as well. If some one starts an endpoint the console send a JSON message with all relevant information, and Wink decodes it to an object. Using the getter methods of the object, the relevant endpoint is stopped. Hope that clarifies your problem. On 16 May 2011 08:43, Amindri Udugala <[email protected]> wrote: > HI Raymond. > > Thank you for the reply > > Thanks for the update. Would you please create a patch and attach it to a > JIRA so that we can review and apply. Instead of big changes, incremental > progress is preferred. > > Will soon attach a patch to, JIRA after applying some more changes > For the endpoint references and endpoints, they can be identified by the > structural uris. For example, componentName/serviceName# > service-binding(bindingName). > > Btw, I don't think we need to manage the Message objects which are created > for each requests to contain context and payload. > > Thanx for the clarification ..... :) > > > > > -- > Thanks > > Amindri Udugala > University of Colombo School of Computing, > Sri Lanka. > > -- Thanks Amindri Udugala University of Colombo School of Computing, Sri Lanka.
