well, I guess we could... I orginally steered away from that idea because it seemed that required the xml to be http encoded. Is that true? I also don't see why we would want the parameter, when it doesn't actually mean anything. The way we're doing it is closer to the way soap works. Whether that's good or bad - I don't know. This is also an external api, so we will be providing the server only. It seems more standard to me to just tell the client to post the xml as the request content instead of as a parameter value, but we're not locked into this. -Ben
On Fri, 25 Mar 2005 07:41:33 -0600, Lars Huttar <[EMAIL PROTECTED]> wrote: > Ben Anderson wrote: > > >Hi, > >What's the easiest way to post xml? Right now I'm using the jakarta > >common's httpclient api. It looks like maybe the cinclude transformer > >might do it, but I can't nail down exactly how. I see that you can > >post parameters as key/value pairs, but that's not what we want. If > >the cinclude doesn't do it, is there another way? > >Thanks, > >Ben > > > > > Why not just post your XML as the value of one of the key/pairs (using > cinclude)? > Can you be more specific about what your constraints are? > > Regards, > Lars > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
