Re: [regrep] ??? Comm. Bootstrapping for ebXML message service

[Farrukh Najmi <Farrukh.Najmi@Sun.COM>]

Kit,

Your understanding is correct. Regardless of the type of client (thick Vs.
thin), the client must discover addressing information (e.g. an HTTP URL) to
each of the concrete service interfaces of the Registry in an out-of-band way.

Typically this means that the client discovers the HTTP URLs either by
word-of-mouth, search engine discovery (e.g. google), discovery of registries
concrete WSDL document in a bootstrap registry.

--
Regards,
Farrukh



Kit Ko wrote:

> Hi farrukh,
>
>    Thanks.  That is to say, even for the thick client the
> transport-specific communication address for the Registry
> should be made "out-of-band".
>
> Regards,
> Kit
>
> Farrukh Najmi wrote:
>
> > Hi Kit,
> >
> > Section 6.6.2.2 is relevant when ebXML Messaging service (ebMS) is used
> > as the registry interface transport. ebMS may be used with thick or thin
> > client and section 6.6.2.2 would be equally applicable.
> >
> > --
> > Regards,
> > Farrukh
> >
> > Kit Ko wrote:
> >
> > > Hi,
> > >
> > >   In "sec 6.6.2.2 Communication Bootstrapping for ebXML message
> > > Service", I think all this
> > > section is only applied to a "thin client" (as defined in sec 6.6.1).
> > > Am I right?!
> > >
> > > Kit
> > >
> > > ----------------------------------------------------------------
> > > To subscribe or unsubscribe from this elist use the subscription
> > > manager: <http://lists.oasis-open.org/ob/adm.pl>
> >
> > ----------------------------------------------------------------
> > To subscribe or unsubscribe from this elist use the subscription
> > manager: <http://lists.oasis-open.org/ob/adm.pl>
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>