Atom App Download Link
Shawnna Breutzmann
1. Export task list (issue query) - copy ATOM link (among export options, see below) on any filtered list and insert the link into an RSS reader. It will show an up-to-date list of tasks matching the filter.
2. Export task overview (detail) - copy ATOM link on a task overview - detail (among export options, see below) and insert the link into an RSS reader. It will show updates from the particular task.
When the RSS reader is installed and you click on ATOM link in Easy Redmine, the following window (or similar) opens, showing you the button "Subscribe" to the RSS feed, and the link that you can copy and insert into your RSS reader directly (this is helpful when the button is missing or doesn't work) as illustrated below.
The ESPI standard uses the Atom standard to provide relationships for the individual ESPI elements in the feed and entries. This reduces the amount of data in a feed: data only need to be provided once. This is done by using the atom "link" metadata to reference ESPI elements found in the feed.
Link relations are a common XML (and HTML) element found across the web. Link relations provide valuable information about content that is in some way related to the current content. A link relation looks like this:
The main advantage over Link headers is that you can have any number of Atom links directly over theconcerned resources, for any number of resources in the response. For example, you can have Atom linksfor the root response entity, and also for each of its children entities.
You can add several @LinkResource annotations on a single method by enclosingthem ina @LinkResources annotation. This way you can add links to the samemethod on several resource types. For example the /order/foo/comments operationcan belongs on the Order resource with the commentsrelation, and on the Comment resource with the listrelation.
When RESTEasy adds links to your resources it needs to insert the right values in the URI remplate.This is done either automatically by guessing the list of values from the entity, or by specifyingthe values in the @LinkResource pathParameters parameter.
Whenever we need to make links for a Book entity, we look up the IDin the Book's @XmlID property. Whenever we make linksfor Comment entities, we have a list of values taken from the Comment's@XmlID and its @ParentResource: the Book andits @XmlID.
The UEL expressions are evaluated in the context of the entity, which means that any unqualifiedvariable will be taken as a property for the entity itself, with the special variable this bound to the entity we're generating links for.
You can restrict which links are injected in the resource based on security restrictions for the client,so that if the current client doesn't have permission to delete a resource he will not be presentedwith the "delete" link relation.
We've seen that both the URI template values and the security constraints of @LinkResourceuse UEL to evaluate expressions, and we provide a basic UEL context with access only to the entitywe're injecting links in, and nothing more.
Sometimes it is useful to add resources which are just containers or layers on other resources. Forexample if you want to represent a collection of Comment with a start indexand a certain number of entries, in order to implement paging. Such a collection is not really an entity in your model, but it should obtain the "add" and "list"link relations for the Comment entity.
Since in most cases the instance of the T type is not directly available in theresource facade, we need another way to extract its URI template values, and this is done by callingthe resource facade's pathParameters() method to obtain a map of URI templatevalues by name. This map will be used to fill in the URI template values for any link generated forT, if there are enough values in the map.
The atom:link element is used throughout the media type as a way to link to other resources. It is the only element in the Atom format that also uses the rel attribute (CL). The initial documentation identifies the following link relation values:
760c119bf3