Overview | Package | Class | Tree | Deprecated | Index | Help
PREV NEXT | FRAMES NO FRAMES

ROME Propono provides a client and server libraries for web publishing via the IETF Atom Publishing Protocol (APP) and the XML-RPC based MetaWeblog API.

See:
Description

Atom protocol Client/Server
com.sun.syndication.propono.atom.client | Client library for interacting with APP web services.
com.sun.syndication.propono.atom.common | Common classes representing APP Service Document.
com.sun.syndication.propono.atom.common.rome | ROME utilities and extensions.
com.sun.syndication.propono.atom.server | Framework for creating server-side APP implementations.
com.sun.syndication.propono.atom.server.impl | Simple APP server implementation that stores entries on disk.

Blog Client
com.sun.syndication.propono.blogclient | Client library for interacting with blog servers
com.sun.syndication.propono.blogclient.atomprotocol | Atom protocol implementation of the BlogClient library.
com.sun.syndication.propono.blogclient.metaweblog | MetaWeblog API implementation of the BlogClient library.

Other Packages
com.sun.syndication.propono.utils | Propopo utilities and exception classes.

ROME Propono provides a client and server libraries for web publishing via the IETF Atom Publishing Protocol (APP) and the XML-RPC based MetaWeblog API. Propono provides:

- Atom Publishing Protocol (APP) client library, which makes it easy for your Java client and server applications to interact with APP services.
- Atom Publishing Protocol server framework, which makes it possible for you to add APP server capabilties to your Java web applications.
- Atom Publishing Protocol file-server sample: a simple file-based APP implementation that stores Atom entries and associated media files in a directory strcuture within your webapp's context directory.
- Blog Client library, which makes it easy for your Java client and server applications interact with blog servers that support either MetaWeblog API or APP.

### Atom protocol packages and dependencies

First, let's cover the Atom packages. If you need to build a Java application that acts as an Atom protocol client, then use the Atom client package `com.sun.syndication.propono.atom.client`. As you can see from the dependency diagram below, it depends on the Atom common package `com.sun.syndication.propono.atom.common` and it uses ROME, JDOM and Apache HTTP Client.

If you are adding Atom server capabilities to your Java web application, then you'll need to use the Atom server package `com.sun.syndication.propono.atom.server`. It depenends on ROME and JDOM.

We provide a file-based Atom server impementation in `com.sun.syndication.propono.atom.server.impl`, which implements the Atom interfaces defined in the server package and provides a simple Atom server that stores entries and associated media files on disk.

### Blog Client packages and dependencies

Now, let's cover the Blog Client packages. The main package is `com.sun.syndication.propono.blogclient`. You'll only need to use to the Blog Client package if you are publishing to legacy systems that don't yet support Atom protocol. By using the Blog Client you can write code that works against both old blog servers that support MetaWeblog API and never servers that support Atom protocol.

As you can see from the dependency diagram below, the MetaWeblog API implementation of the Blog Client uses Apache XMLRPC 3.0 and the Atom protocol implementation uses the Atom client.

For more information on the packages, refer to the Javadoc package summary pages.

Overview | Package | Class | Tree | Deprecated | Index | Help
PREV NEXT | FRAMES NO FRAMES