Btw, I don't think we need to manage the Message objects which are created for
each requests to contain context and payload.
Sent from my iPad
On May 15, 2011, at 1:27 AM, Amindri Udugala <amindriudug...@gmail.com> wrote:
> Hello,
>
> Here is an update of my work so far,
>
> I created a new jmx module in the modules folder. There I created MXBean
> interfaces for some runtime components,
> Here are the runtime components,
> EndpointReference
> Message
> ProviderfactoryextensionPointRuntimeComponentreference
> RuntimeComponentReference
> RuntimeComponentService
> RuntimeWireProcessorExtensionPoint
> RuntimeWireProcessor
> and all other interfaces implementing ProviderFactory interface
>
> (please mention if I need to add more runtime components)
>
>
> These MXBean interfaces are implemented in classes , in "mgt" sub package
> which I created in tuscany-spi-core,
> I've got few more questions before proceeding....
>
> When I was going through the Message interface, I understood that neither of
> two implementation classes set the messegeID
>
>
> public Object getMessageID() {
> return null;
> }
>
> public void setMessageID(Object messageId) {
> throw new UnsupportedOperationException();
> }
>
>
> Since many messages can be generated I think it is important to identify
> message uniquely. When implementing the JMX management console I propose to
> use JSON messages for communication (Wink can be used for this). If a user
> needs to change, set or view the message body, of a particular message how to
> uniquely identify the message?
>
> The same problem exists with other interfaces (eg EndpointReference) as well
> (No way to uniquely identify objects). This would not be a problem if only
> one object is created from each runtime components. Or may be that I
> misunderstood the whole procedure. Please correct me if I'm wrong
>
>
> --
> Thanks
>
> Amindri Udugala
> University of Colombo School of Computing,
> Sri Lanka.
>
