• Post Reply Bookmark Topic Watch Topic
  • New Topic

Soap to compete J2EE ?  RSS feed

 
JeanLouis Marechaux
Ranch Hand
Posts: 906
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,
I'm a newbee in the Soap world, so I need some Soap gurus here.

Do you see SOAP as an serious alternative (competitor) to J2EE EJB-RMI ?
 
peter rapier
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What I've seen is this:
SOAP just gives us a way to agree on how to get a message from point A to point B, with the semantics of invoking a procedure. What goes on at the receiving end, that is the place where the service is, may be implemented with J2EE or COM+ or other menas to actually do some work. So they are not necessarily competing.
 
JeanLouis Marechaux
Ranch Hand
Posts: 906
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Ok Peter, but what about the method invocation ?
Soap uses HTTP to call a method and obtain the answer.
And UDDI, WSDL are used to locate the service, and then call the method.
So how does it fits with JNDI lookup and RMI in the J2EE plateform ?
 
Kyle Brown
author
Ranch Hand
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
SOAP isn't a competitor -- it's a complement to J2EE. SOAP doesn't specify how the objects on each end are implemented -- J2EE provides that. SOAP specifies a vendor and language-transparent protocol for messaging -- J2EE needs that for interoperation with anything else (including interoperation between different J2EE vendor's containers) I don't think one will replace the other.
Kyle
------------------
Kyle Brown,
Author of Enterprise Java (tm) Programming with IBM Websphere
See my homepage at http://members.aol.com/kgb1001001 for other WebSphere information.
 
JeanLouis Marechaux
Ranch Hand
Posts: 906
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanx Kyle.
Soap is now a little bit clearer for me.
Originally posted by Kyle Brown:
SOAP isn't a competitor -- it's a complement to J2EE. SOAP doesn't specify how the objects on each end are implemented -- J2EE provides that. SOAP specifies a vendor and language-transparent protocol for messaging -- J2EE needs that for interoperation with anything else (including interoperation between different J2EE vendor's containers) I don't think one will replace the other.
Kyle

 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!