geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alan Cabrera <...@toolazydogs.com>
Subject RE: WebServices & UI team
Date Wed, 13 Aug 2003 23:25:51 GMT
SOAP can be embedded underneath JMX remote if one wanted to.  My question
is, why have a SOAP interface for server management when JMX fits the bill?
I am wary of a proliferation of management APIs unless I am mistaken and
there is a SOAP spec out there for the management of J2EE servers.

> -----Original Message-----
> From: Noel J. Bergman [mailto:noel@devtech.com] 
> Sent: Wednesday, August 13, 2003 6:51 PM
> To: geronimo-dev@incubator.apache.org
> Subject: RE: WebServices & UI team
> 
> 
> > Why a webservice interface when JSR160 handles it?
> 
> JSR 160 (aka Remote JMX) provides the necessary interface, 
> but AIUI JSR 160 is Java-centric.  A web service (aka SOAP) 
> interface would be decoupled from Java RMI/serialization.  
> What I thought was being said was that:
> 
>   - JMX provides the singular management interface
>   - JSR 160 provides a remote interface to JMX
>   - A WSDL interface could also be defined.  The
>     IMPLEMENTATION would call the JMX interface.
> 
> A WSDL (http://www.w3.org/TR/wsdl) interface would provide a 
> language neutral management interface.
> 
> 	--- Noel
> 

Mime
View raw message