Re: SOAP - How it works?

Hi,

On 12/2/07, Yohan Liyanage <[email protected]> wrote:
> Ok, What I need to know is this.
>
> In JMX, when we need to invoke a method on a MBean, that request will be
> sent to the MBeanServer, and then the server will forward the request to the
> MBean, and return the results to us. Generally, this happens through RMI,
> because the Sun Reference Implementation for JMX makes use of RMI
> Connectors.
>
> However, MX4J provides alternative connectors, such as SOAP, Burlap etc.
> However, if SOAP over HTTP is used, then there will be the usual limitations
> of HTTP, such as client initiated dialogues (1), as I have mentioned before.
>
> That means that the MBean Server cannot invoke methods on the MBeans
> directly (becuase the server cannot initiate a dialogue), unless the MBeans
> send a request to the MBeanServer first.

In JMX the server side never invokes (as in initiating the remote
call) the client side, nor via RMI nor via any other protocol
implementation. MX4J is no exception to this.

> A solution for this would be embedding a SOAP Server inside the client side
> as well, which provides an interface for the MBeanServer to invoke methods
> on MBeans.
>
> I would like to know the MX4J's solution for this issue.

As I see it there is no issue, as there is no need for a server to
invoke the client side.

If you wanted to know if a JMX connector server invokes a JMX
connector client, then this never happens.

Simon
-- 
http://bordet.blogspot.com

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4