Another way would be to write another marshaler that will specifially handle post requests and configure it on the endpoint. I'd like to keep the endpoint free of properties that are not generic. In addition to the marshaler, we could add another endpoint if needed, so that you can configure the properties on a HttpPostProviderEndpoint (which would use the post marshaler by default).
On 11/5/07, MrRothstein <[EMAIL PROTECTED]> wrote: > > > I would like to take a crack at SM-580. The patch attached seems to apply > to > the HttpEndpoint. I would like to do make the fix for > HttpProviderEndpoint. > > It seems easy enough: > Add property to endpoint > Set property to marshaller in endpoint init > Have the marshaller look up property (same as contentType/locationUri) > prior to formatting http request > > Is that about right? > > My only issue with this is figuring out what to do if the contentType does > not evaluate to post, should the existence of a post parameter override > content type or an exception raised? > > Thanks > -- > View this message in context: > http://www.nabble.com/SM-580-tf4754351s12049.html#a13595419 > Sent from the ServiceMix - Dev mailing list archive at Nabble.com. > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
