Ok, thanks. Then it's ok from the client side (.NET) Have you seen any example how to implement the intermediary server? Do I need to implement a handler in Axis or is it provided?
We will have [.NET WS Client] <-> [J2EE intermediary] <-> [J2EE WS Provider] And my domain is the intermediary server. // Jocke > -----Original Message----- > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > Sent: den 11 augusti 2003 15:14 > To: [EMAIL PROTECTED] > Subject: Re: WS-Routing > > > .NET WSE includes support for WS-Routing. > http://msdn.microsoft.com/webservices/building/wse/ > > ----- Original Message ----- > From: "J�rkeborn, Joacim (JJ.)" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, August 11, 2003 9:01 AM > Subject: RE: WS-Routing > > > > Ok, then I think that WS-Adressing is not an option for us > today. How > about > > WS-Routing? Is this implemented in .NET? > > > > Have anyone seen an example in Java where this technology > is used? Can > > "samples.proxy.ProxyService" do the same job? > > > > // Jocke > > > > > -----Original Message----- > > > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > > > Sent: den 8 augusti 2003 12:52 > > > To: [EMAIL PROTECTED] > > > Subject: Re: WS-Routing > > > > > > > > > John Shewchuk from Microsoft informed me that WS-Routing has been > > > "superceded" by WS-Addressing, although I don't think > that .NET WSE > > > supports WS-Addressing yet. > > > > > > Axis supports any type of header processing, including > WS-Routing, > > > but you need to implement a handler to do the processing. > > > > > > Anne > > > > > > ----- Original Message ----- > > > From: "J�rkeborn, Joacim (JJ.)" <[EMAIL PROTECTED]> > > > To: <[EMAIL PROTECTED]> > > > Sent: Friday, August 08, 2003 4:50 AM > > > Subject: WS-Routing > > > > > > > > > > Hi, > > > > > > > > Is WS-Routing supported in Axis (in what version of Axis)? > > > > > > > > I will use WebSphere Application Server and WSAD. > > > > > > > > // Jocke > > > > > > > > > >
