Graham Charters wrote:
> 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 wan
Graham Charters wrote:
> For the XML serialization using the default namespace, would we want
> this to be determined from the XML schema? So for example, our
> Atom1.0.xsd has the default namespace being that of Atom, so the
> instance documents could do the same.
Yes, I think that would be th
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.
The many-valued nature of a lot of the properties is unfortunately due
to the inability of XML schema to accurately describe the Atom
Syndication Format. It's a while since I wrote the schema, but I seem
to recall it was to do with the use of . The Atom XML is defined in terms of Relax NG which
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'
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 de
Matthew Peters wrote:
>
> I hoped we had seen the back of namespace problems
Told you so: http://groups.google.com/group/phpsoa/msg/11a5c7ea4f6dd260 :-)
> I will open a JIRA.
You'll have noticed that Pete has provided fixes for
http://issues.apache.org/jira/browse/TUSCANY-1564 and
http://i
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
Oh dear.
>
> Caroline Maynard
>
.../...
> atom namespace. However the problem for me is that this particular
> server still doesn't like it - it gives me a response code 400, but
I hoped we had seen the back of namespace problems but this looks like
Tuscany is still generating the wrong XML.
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
Caroline Maynard wrote:
> 5.Server rejected the generated XML
> I use the following code to generate my feed entry:
>
> $xmldas = SDO_DAS_XML::create("Atom1.0.xsd");
> $document = $xmldas->createDocument(
> "http://www.w3.org/2005/Atom";, 'entry');
> $entry = $document->getRootDataObject();
11 matches
Mail list logo
