Re: [ebxmlms-general] Request object

[Ng C. Y. [Cyng] <cy...@cs...>]

Hi,

> Unfortunately, it seems as if the Request object always sends the
> message to the MSH that was specified upon instantiation, regardless of
> what I pass in using MessageHeader.addToPartyId().  Am I
> missinterpretting the function of adding a "to party" to an ebxml
> message as header?

        In msh.properties.xml, there is a property <ToUrlResolver>. You
can uncomment it to hk.hku.cecid.phoenix.message.handler.ToUrlResolverImpl.

        This mechanism works as follows. If such a ToUrlResolver
implementation does not exist, Request will always use toMshUrl (specified
upon Request instantiation). Otherwise, ToUrlResolver will try to examine
the <To><PartyId> in the ebXML message to see if it is a resolvable URL
with supported transport protocol, say, http://, and this URL will be used
then. However, if the <To><PartyId> is not resolvable, say, urn:oasis:,
Request falls back to use toMshUrl. So, you can implement your own
ToUrlResolver and set it in msh.properties.xml to map those schema names
like urn:oasis: to a physical URL of HTTP or Mail.

        Hope this help!

Regards,
CY

----------------------------------------------------------------------------
Ng Chi Yuen, CY.       cy...@ce...       http://www.cecid.hku.hk/
Technology Officer,
Centre for E-Commerce Infrastructure Development,
The University of Hong Kong
----------------------------------------------------------------------------