|
Replies:
1
-
Last Post:
Feb 27, 2009 4:17 AM
by: Potociar Marek
|
|
|
|
|
|
|
Architecture: WSIT Integration into Metro
Posted:
Feb 27, 2009 4:17 AM
|
|
|
|
|
|
|
|
|
|
Re: Architecture: WSIT Integration into Metro
Posted:
Feb 27, 2009 4:17 AM
in response to: Guest
|
|
|
|
|
Hello Nicolas,
The Metro processing tubeline is based on the chain of filters/
interceptors design pattern. Still, it is orthogonal to the notion of
JAX-WS SOAPHandler. Metro processing tubeline is the heart of
"streamlined" SOAP message processing concept in Metro. As such it is
a Metro-specific implementation detail and has no connection to JAX-WS
API or specification. To dive a little deeper, one of the tubes which
is a part of the Metro tubeline is a HandlerTube which is responsible
for invoking registered JAX-WS SOAPHandlers. So basically all JAX-WS
handler processing takes place at one single predefined place in the
whole Metro tubeline. You can view JAXWS handlers as a high-level and
portable API for processing SOAP messages, while Metro tubes are non-
portable, low-level (but very flexible and powerful) SOAP message
handlers/processors.
Hope that answered your question.
Regards,
Marek
On 27.2.2009, at 12:59, Nicolas Berner wrote:
> Hi Marek,
>
> thanks for this link. That´s a very interesting presentation.
>
> I knew this picture on slide 7 already. I can imagine what is
> happening during the processing pipeline but just for the big
> picture in my head:
> Is this process pipe just a kind of SOAPHandler-Chain in JAX-WS-
> Architecture?
> incoming ClientRequest -> EndpointListener/Dispatcher ->
> mustUnderstanding and Processing -> SOAPHandler + METRO PROCESSING
> PIPELINE -> Java/XML-Binding ->Service Endpoint -> vice versa
>
> Thanks,
> Nicolas
>
>
> 2009/2/27 Potociar Marek <Marek.Potociar@sun.com>
> (moving the discussion to Metro users forum)
>
> Hello again,
> yesterday our lead architect Harold Carr held a webinar where he
> touched your topic as well. Here's a link to the slideshow:
>
> http://www.slideshare.net/pelegri/2009-02-26-metro-glass-fish-webinar
>
> the graphics you were interested in are on the slide 7.
>
> Thanks,
> Marek
>
> On 26.2.2009, at 19:28, Potociar Marek wrote:
>
>> Hello Nicolas,
>> I could not quickly find any graphics, but in general your
>> assumption is correct. This is the processing flow:
>>
>> Client App request --> Metro client tubeline --> client transport --
>> > network --> server transport --> Metro server tubeline -->
>> Service endpoint (Business logic)
>>
>> ...any response returned from the service to client goes in exactly
>> opposite direction.
>>
>> Hope that helped,
>> Marek
>>
>> On 26.2.2009, at 15:00, Nicolas Berner wrote:
>>
>>> Hi Everybody,
>>>
>>> I´m quite new to WSIT and Metro. I have a question concerning the
>>> architecture of WSIT together with JAX-WS.
>>>
>>> I found a presentation of Arun Gupta. Available here: http://weblogs.java.net/blog/arungupta/archive/metro-midwest07.pdf
>>> On the last page he shows the Processing Pipeline of Metro. I
>>> think WSIT is involved in this pipeline because the main parts of
>>> WSIT (Security, Reliability,...) are called during the processing.
>>> Am I right?
>>> My problem is that I don´t know where JAX-WS or my WebService-
>>> Implementation is called. Is it after the Processing Pipeline? I
>>> assume that.
>>> Does anyone have a link to a graphic of the whole flow of my Web
>>> Service Request and Response?
>>>
>>> I hope you folks understand my problem.
>>>
>>> Thanks in advance,
>>> best regards,
>>> Nicolas
>>
>
>
[att1.html]
|
|
|
|
|
java.net RSS
