Re: SOAP - How it works?

simonebordet wrote:
> 
> hi,
> 
> On 12/1/07, Yohan Liyanage <[email protected]> wrote:
>> MX4J Supports SOAP based MBean Servers.
>>
>> However, when running over HTTP, only clients can initiate a conversation
>> with the server. (Ex, Client connects to server and makes a request. But
>> a
>> server cannot connect to a client directly and send something, unless the
>> client initiated the conversation first)
>>
>> So, how does the MX4J SOAP based MBean Servers allow to invoke methods on
>> the deployed MBeans ?
> 
> I am not sure I understood your question; the paragraph just above and
> the one above that seem to me totally unrelated.
> Can you rephrase explaining what is your doubt ?
> 
> 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
> _______________________________________________
> Mx4j-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mx4j-user
> 
> 

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. 

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.


Thanks !
-----------

(1) - An example for this would be, in the Web, the browser needs to connect
to the server and make a request first. Then the server will respond. But
the server cannot connect to the client (browser) directly and send
something.
-- 
View this message in context: http://www.nabble.com/SOAP---How-it-works--tf4927406.html#a14113050
Sent from the MX4J - User mailing list archive at Nabble.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