[ebxmlms-develop] Missing access to payload descriptions

[Gait B. <gai...@ti...>]

While building a tool that would return a copy of the incoming message, =
we found out that there is no public way to access the payload =
descriptions that are in the Manifest. In fact, the entire Manifest is =
made private. I'd suggest to open up an API to the manifest, such that a =
payload can be added to the message with or without a description and =
additional descriptions can be added after that, with the appropriate =
language identifiers. Additionally, we need a way to retrieve the =
descriptions from the payload, either by looking up the correct =
reference in the Manifest and go from there, or as an API on the payload =
object from the ebXML message.
It's nice that you can now add a payload with a description, but it's =
not very useful unless you can also retrieve it, and are able to add and =
retrieve multiple descriptions.

thnx, Gait.

PS, note that payload descriptions are not the same as the descriptions =
in the message header.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Gait Boxman
Manager Advanced Technology & Standards
TIE Product Development BV
Amsterdam, The Netherlands
Tel: +31 20 658 9091  Fax: +31 20 658 9945
E-mail: gai...@ti...  WWW: www.TIEglobal.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~