I meant to ask. Of the options to improve the API, which would people
prefer, or are there any other suggestions?
My current preference is for the building up of the SDO Atom model
programmatically because this will not require the developer to
specify they want to use something other than SDO.
Matthew Peters wrote:
Thank you. The mistake I was making was putting
$entry_author-name = $author;
when I should have had
$entry_author-name[] = $author;
Isn't it all horrid. When you try to write it from scratch, and if you
do not know what you are doing (that was me) it's
How beastly of it. Now, who wants to be the one to tell Pete...
On Aug 22, 11:33 am, Caroline Maynard [EMAIL PROTECTED] wrote:
However I am still getting the 400 status code (with no error message)
from the atompub server. I think the code in question just can't cope
with not having a
On Aug 20, 12:10 pm, Caroline Maynard [EMAIL PROTECTED] wrote:
Matthew Peters wrote:
Incidentally, could you paste in a little of the code that used to add
the fields to the entry? I am finding it very hard to write the code
that creates an entry - something to do with the weird
Matthew Peters wrote:
I've been looking at problem 5 in your list here - the server
rejecting the generated XML. I think our Atom1.0.xsd is wrong.
Our xsd has no elementFormDefault attribute on the schema definition.
This means that we get the default behaviour, which is that only top
