RE: [uddi-dev] Multiple access points II

[John Colgrave <colgrave@hursley.ibm.com>]

Paul,

The new Technical Note on using WSDL and UDDI, being developed by the OASIS
UDDI Specifications Technical Committee, restricts a UDDI businessService to
represent at most one WSDL service so if Explode is one WSDL service and
Implode is a different WSDL service then they should be represented as
different UDDI businessServices.

This Technical Note should be released in the not-too-distant future.

John Colgrave
IBM


-----Original Message-----
From: psterk@phys-hanwk16-2.ebay.sun.com
[mailto:psterk@phys-hanwk16-2.ebay.sun.com] On Behalf Of Paul Sterk
Sent: 07 March 2003 01:30
To: uddi-dev@lists.oasis-open.org
Subject: [uddi-dev] Multiple access points II


Hi,

Second question regarding multiple access points per service. A proposal has
come up to allow someone to register a service and have multiple
accessPoints for the service.  The issue here is that each accessPoint
points to a different service.

Let me give an example:

The service is registered as Bill of Materials.  It has two accessPoints:

Bill of Materials Explode
http://hostname/bomExplode

Bill of Materials Implode
http//hostname/bomImplode

These are two different services with different associated WSDL docs.

I am personally uncomfortable with this model because I believe that each
businessService should be mapped to one service implementation. I feel that
BOMExplode and BOMImplode are two different services and should be
registered separately.

However, I would like here what your experience and opinions are in this
area.

If this model is acceptable, how do you find a specific accessPoint
programmtically (JAXR) in UDDI v2.0?  Do you use the tModelInstanceDetails
object?

Any feedback in this regard would be very helpful.

Thanks,
Paul