ws-rx message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: RE: [ws-rx] i061 proposal / directions
- From: Christopher B Ferris <chrisfer@us.ibm.com>
- To: ws-rx@lists.oasis-open.org
- Date: Wed, 25 Jan 2006 05:45:28 -0500
Premature optimization strikes again!
Cheers,
Christopher Ferris
STSM, Emerging e-business Industry Architecture
email: chrisfer@us.ibm.com
blog: http://www.ibm.com/developerworks/blogs/dw_blog.jspa?blog=440
phone: +1 508 377 9295
"Gilbert Pilz" <Gilbert.Pilz@bea.com>
wrote on 01/24/2006 11:26:20 PM:
> Rich,
>
> I don't think Lei was saying that *every* SOAP intermediary needs
to
> have knowledge of the WSDL of the ultimate destination, just that
some
> nodes may and that these nodes may elect to return a 202 before they
> have any knowledge of the results of subsequent downstream processing
> (obviously they would only elect to do this in the case of one-way
> operations).
>
> - g
>
> > -----Original Message-----
> > From: Richard Salz [mailto:rsalz@us.ibm.com]
> > Sent: Tuesday, January 24, 2006 7:01 PM
> > To: Lei Jin
> > Cc: Doug Davis; ws-rx@lists.oasis-open.org
> > Subject: RE: [ws-rx] i061 proposal / directions
> >
> > "Lei Jin" <ljin@bea.com> wrote on 01/24/2006
08:39:35 PM:
> >
> > > For example, in an ESB implementation, an intermediary can
hold a
> > > bunch of WSDLs for a number of backend services that it
routes
> > > messages to.
> >
> > I think it would be a real bad idea to make WSDL a
> > requirement. You really don't want to require every
> > intermediary to have prior knowledge of all WSDL files for
> > every message that it might ever see. It'd be hard to call
> > that "loosely coupled."
> >
> > /r$
> >
> > --
> > SOA Appliance Group
> > IBM Application Integration Middleware
> >
> >
> >
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]