Hi Nirmal, If you have gone through networking concepts, you might have know about the routing machanism. Let me explain you for web services.
1. Suppose 'A' is a Client (Web Service Requester) placed in China. 2. 'B' is a Web Service Provider Placed in US. Now If A is requesting for certain web service from B. A will have to send a 'SOAP' request to B. But this request cant to go directly to B as there might be multiple server/machines in the path from A to B, say X is a in between machine. So the path is A-->X-->B Now X should be able to understand SOAP request send from A and will forward this request to B. Then again will recieve SOAP response from B and forward it to A. Thus X should be able to understand the SOAP message send between A and B. Here X is called as SOAP intermediary. Hope this helps Regards Deepak Singh On Fri, Jul 3, 2009 at 4:58 PM, Nirmal Kumar <nirmal.h...@gmail.com> wrote: > Hi Alexey, > > Sorry I really didn't get what you're trying to explain. > > My question again: > > When exactly does these *SOAP Intermediaries* come into picture? > Because as a practical example I developed and deployed a Web Service in > BEA WebLogic Server. > Now from the BEA Workshop itself I generated the Client(jar) for the Web > Service. > Next I developed a Java Client and used the generated Client(jar) to invoke > the method of the Web Service that I developed and deployed earlier. > > I was successfully able to invoke the method of the Web Service.* That's > it.* > > Also from the Test Browser I was able to see the SOAP Request and SOAP > Response. > Now tell me where does these SOAP Intermediaries come into picture in my > example. > > Also do I've to worry about the SOAP Intermediaries when developing Web > Services? > > > Thanks, > Nirmal > > > > \\\/// > / \ > | \\ // | > ( | (.) (.) |) > ----------o00o--(_)--o00o------------------- > Stand up,be bold,be strong. > Take the whole responsibility on > ur own shoulders and know that > U are the creator of ur own destiny. > ------ooo0------------------------------------- > ( ) 0ooo > \ ( ( ) > \_) ) / > (_/ > > > On Fri, Jul 3, 2009 at 4:35 PM, Alexey Filippov <alexey.filip...@gmail.com > > wrote: > >> Hi Nimal, >> Think of SOAP intermediary as of proxy server. It can be a separate box or >> a separate servlet, or the same servlet calling itself, it doesn't matter. >> >> What matters is that it receives the request, processes it, sends to >> server (which in turn amy be an intermediary, too), receives the answer, >> processes it, and returns to the caller. >> >> It may be useful for: >> * Load balancing >> * Authorization >> * Maintaining previous versions of web services >> * Adapters for (ever-changing) third-party services >> >> etc. >> >> Cheers, >> >> Alf >> >> 2009/7/2 Nirmal Kumar <nirmal.h...@gmail.com> >> >>> Hi All, >>> >>> Web Service is a very broader term and is not specific for J2EE or .NET >>> or any other platform. >>> >>> The basics (*SOAP*, *WSDL*) are however same for all the platforms that >>> is why it provides cross-platform, distributed computing. For e.g. a Java >>> Client can invoke a method of a web Service implemented by a .NET platform >>> or vice-versa. >>> >>> I've doubts in understanding the following core concepts of *SOAP*: >>> A SOAP message travels along the *message path *from a sender to a >>> receiver.*(DOUBT)* >>> As a SOAP message travels along the message path, its header blocks may >>> be intercepted and processed by any number of *SOAP intermediaries*along >>> the way. >>> *(DOUBT)* >>> A SOAP intermediary is both a receiver and a sender. It receives a SOAP >>> message, processes one or more of the header blocks, and sends it on to >>> another SOAP application. *(DOUBT)* >>> The applications along the message path (the initial sender, * >>> intermediaries*, and ultimate receiver) are also called *SOAP nodes*.* >>> (DOUBT)* >>> >>> >>> When exactly does these *SOAP Intermediaries* come into picture? >>> Because as a practical example I developed and deployed a Web Service in >>> BEA WebLogic Server. >>> Now from the BEA Workshop itself I generated the Client(jar) for the Web >>> Service. >>> Next I developed a Java Client and used the generated Client(jar) to >>> invoke the method of the Web Service that I developed and deployed earlier. >>> I was successfully able to invoke the method of the Web Service.* That's >>> it.* >>> >>> Also from the Test Browser I was able to see the SOAP Request and SOAP >>> Response. >>> >>> Now tell me where does these SOAP Intermediaries come into picture in my >>> example. >>> >>> >>> From my understanding, it's only client / server - request / response, >>> one-one communication. >>> But when I read SOAP specification, it may have many SOAP Intermediaries >>> between the web service client and server. >>> >>> >>> 1. What is SOAP Intermediaries used for? >>> 2. Does use of SOAP Intermediaries happen often in the real world >>> industry? >>> 3. What are example of SOAP Intermediaries and use of it? >>> 4. Are those SOAP Intermediaries just another SOAP engine (e.g. axis) >>> sit on another Computer / Host? >>> 5. I also read in the specification that SOAP Intermediaries modify >>> the SOAP request / response too why they need to do so? >>> 6. I saw a lot web service at www.xmethods.net they are all one-one >>> --> request / response, did all the web services there ever use SOAP >>> Intermediaries? Am I sending request to SOAP Intermediaries or Ultimate >>> soap >>> receiver? Usually it will have 1 request, and then response XML when i >>> click >>> on "*Try It*" there. >>> >>> >>> >>> Thanks, >>> Nirmal >>> >>> \\\/// >>> / \ >>> | \\ // | >>> ( | (.) (.) |) >>> ----------o00o--(_)--o00o------------------- >>> Stand up,be bold,be strong. >>> Take the whole responsibility on >>> ur own shoulders and know that >>> U are the creator of ur own destiny. >>> ------ooo0------------------------------------- >>> ( ) 0ooo >>> \ ( ( ) >>> \_) ) / >>> (_/ >>> >>> >>> On Thu, Jul 2, 2009 at 3:50 PM, Norberto Jr. Pedroza < >>> totongpedr...@hotmail.com> wrote: >>> >>>> I knew a little about webservice but in .Net C#. >>>> I created a Web service class separate from the Client or front end >>>> application. >>>> The client application will use this web service class by >>>> referencing this in the client application. >>>> This web service class should be installed or should be put to the >>>> Server. >>>> Since the client has reference to the webservice class, it can used all >>>> the public methods of the webservice class >>>> by calling the method name through request then the server execute the >>>> request and send xml data. >>>> >>>> But in java i have no idea how the webservice works. >>>> >>>> Bert >>>> >>>> ------------------------------ >>>> From: nirmal.h...@gmail.com >>>> Date: Thu, 2 Jul 2009 11:09:37 +0530 >>>> Subject: [java ee programming] Doubt about SOAP !!!!!! >>>> To: java-ee-j2ee-programming-with-passion@googlegroups.com >>>> >>>> >>>> Hi All, >>>> >>>> I'm new to web services and just started learning the basics i.e. SOAP, >>>> WSDL. >>>> >>>> *According to my understanding:* >>>> The *Client *sends a SOAP request to the *Receiver*. >>>> The *Receiver *then finally sends the SOAP response to the *Client*. >>>> >>>> But in books its mentioned : >>>> All SOAP messages start with the initial sender(*Client*), which >>>> creates the SOAP message, and end with the ultimate receiver(*Web >>>> Service*).*(OK) >>>> >>>> *A SOAP message travels along the *message path *from a sender to a >>>> receiver.*(DOUBT)* >>>> As a SOAP message travels along the message path, its header blocks may >>>> be intercepted and processed by any number of *SOAP intermediaries*along >>>> the way. >>>> *(DOUBT)* >>>> A SOAP intermediary is both a receiver and a sender. It receives a SOAP >>>> message, processes one or more of the header blocks, and sends it on to >>>> another SOAP application. *(DOUBT)* >>>> The applications along the message path (the initial sender, * >>>> intermediaries*, and ultimate receiver) are also called *SOAP nodes*.* >>>> (DOUBT)* >>>> >>>> *I'm having a following doubt:* >>>> Why we are having the *SOAP Intermediaries* ? >>>> Since we only have a Client and the Receiver(*Web Service*).For >>>> example, I've a *Java Client* that invokes a method of the *Web Service >>>> *. >>>> >>>> Please help me in understanding the core concept as well as the context >>>> in which this *SOAP Intermediaries *are being talked about. >>>> A practical example would be great. >>>> >>>> Thanks, >>>> Nirmal >>>> \\\/// >>>> / \ >>>> | \\ // | >>>> ( | (.) (.) |) >>>> ----------o00o--(_)--o00o------------------- >>>> Stand up,be bold,be strong. >>>> Take the whole responsibility on >>>> ur own shoulders and know that >>>> U are the creator of ur own destiny. >>>> ------ooo0------------------------------------- >>>> ( ) 0ooo >>>> \ ( ( ) >>>> \_) ) / >>>> (_/ >>>> >>>> >>>> >>>> ------------------------------ >>>> Make the most of what you can do on your PC and the Web, just the way >>>> you want. Windows Live <http://www.get.live.com/wl/all> >>>> >>> >>> >>> >>> >> >> >> -- >> Alexey "Alf" Filippov >> > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Java EE (J2EE) Programming with Passion!" group. To post to this group, send email to java-ee-j2ee-programming-with-passion@googlegroups.com To unsubscribe from this group, send email to java-ee-j2ee-programming-with-passion+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/java-ee-j2ee-programming-with-passion?hl=en -~----------~----~----~----~------~----~------~--~---
