Rome Atom library

[Richard Jones]

Folks, I've done my level best to get ATOM serialisation for ORE
resource maps to work through the ROME library, but it just simply isn't
up to the job. It fails to serialise parts of the model, despite their
presence, and has an appalling abstraction over all syndication feed
types. I'm going to have to migrate to an atom library that works; does
anyone have any suggestions (Apache Abdera experience anyone? Restlet
ATOM model?).

Cheers,

Richard

--
=======================================================================
Richard Jones | Hewlett-Packard Limited
Research Engineer, HP Labs | registered office:
Bristol, UK | Cain Road, Bracknell,
| Berks, RG12 1HN.
| Registered No: 690597 England
eml: richard...@hp.com -------------------------------------
blg: http://chronicles-of-richard.blogspot.com/
-----------------------------------------------------------------------
The contents of this message and any attachments to it are confidential
and may be legally privileged. If you have received this message in
error, you should delete it from your system immediately and advise the
sender. To any recipient of this message within HP, unless otherwise
stated you should consider this message and attachments as "HP
CONFIDENTIAL".
========================================================================

[Richard Jones]

That said, I've had a lot more luck this afternoon, and have "resolved"
all but one of the serialisation problems. It appears that some
elements do not render unless some other elements (unrelated as far as I
can tell) are present. I have only one outstanding problem with regard
to Rome, which is that it does not serialise the title attribute of a
link tag. grr.

Anyway, I've checked in today's changes and you will find a
significantly improved atom serialisation

Cheers,

Richard

[scottw]

I'd stick with Rome if I were you - you can find access to the rest of
the Atom model at WireFeed level. If there are any parts of the common
model that don't work, post them up on the Rome-dev list; as a
workaround you might find it makes sense to make a new Rome Module to
ensure serialization happens the way you want it to - though I don't
know how Rome would handle namespace conflicts in its own modules...

I've tried Abdera but rapidly removed it very soon after - you end up
with the whole of the Apache stack in your dependency list for no
particularly good reason. Rome is very neatly self-contained so much
more suitable for library use.

> > eml: richard.d.jo...@hp.com       -------------------------------------

> > blg:http://chronicles-of-richard.blogspot.com/
> > -----------------------------------------------------------------------
> > The contents of this message and any attachments to it are confidential
> > and may be legally privileged. If you have received this message in
> > error, you should delete it from your system immediately and advise the
> > sender. To any recipient of this message within HP, unless otherwise
> > stated you should consider this message and attachments as "HP
> > CONFIDENTIAL".
> > ========================================================================
>
> --
> =======================================================================
> Richard Jones                     |       Hewlett-Packard Limited
> Research Engineer, HP Labs        |       registered office:
> Bristol, UK                       |       Cain Road, Bracknell,
>                                   |       Berks, RG12 1HN.
>                                   |       Registered No: 690597 England

> eml: richard.d.jo...@hp.com       -------------------------------------