Keith, To complete WODEN-148, I need to make sure I understand your use case for handling HTTP location templates and doing the required encoding.
I originally assumed that you do things in this sequence: 1. substitute HTTP location templates with element values from the instance data 2. combine the Endpoint address with the HTTP location to form a URI 3. Do the necessary encoding on the resulting URI That sequence means you would need to know where raw templates had been used to avoid encoding those substituted values in the URI. An alternative approach (and perhaps this is how you do it) would be to: 1. substitute the HTTP location templates with values from the instance data that you have already encoded 2. then combine the Endpoint address with the HTTP location to form a URI The second approach is easier to support in Woden because we don't need to track the position of substituted raw templates. Does either approach match your use case? thanks, John Kaputin Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
