Re: ANN: WS Routing sync request-response endpoint for the HP Web Services platform

Bob Cunnings <[email protected]> Mon, 15 Apr 2002 19:49:09 -0600
Newsgroups gmane.comp.windows.devel.soap.rp
Message-ID <02ef01c1e4e8$e70318d0$0301a8c0@delta>
Hello,

Looks good, I've added it to the White Mesa WS-Routing test client at:
http://www.whitemesa.net/ws-rp/echoString_ws-rp.htm
as an available endpoint node.

It's nice to see another WS-Routing node up for testing. Initial tests =
using one or more of the intermediaries available have positive results, =
although it appears that the EarthConnect intermediary is unavailable. =
For example path:

client =3D> 4s4c =3D> White Mesa =3D> SQLData =3D> HP

works fine. The extra header "logResults" in the response comes courtesy =
of the 4s4c intermediary!

RC

> Hi,
>=20
> A prototype WS-Routing service endpoint deployed using the HP Web =
Services
> Platform 2.0 release
> (http://www.hpmiddleware.com/products/hp_web_services/default.htm)
> is now available at http://soap.bluestone.com/hpws/soap/WsRoutingTest
>=20
> This endpoint currently supports only synchronous request-response
> invocations, and it cannot act as a WS Routing intermediary.
>=20
> The wsdl for the endpoint is the same as that used by the =
whitemesa.net WS
> Routing
> endpoint (http://www.whitemesa.net/wsdl/interop_base_end.wsdl).
>=20
> Regards,
> Shridhar Diwan: [email protected]
> William Vambenepe: [email protected]