Restlet 1.1.0 (Testing branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Restlet 1.1.0 (Testing branch)
# 1  
Old 10-28-2008
Restlet 1.1.0 (Testing branch)

Restlet is a REST framework for Java. It supports all REST concepts (Resource, Representation, Connector, Component, etc.) and is suitable for both client and server Web applications. It supports major Web standards like HTTP, SMTP, XML, JSON, WADL, and Atom. Many extensions are also available to integrate with Servlet, Spring, Jetty, Grizzly, Simple, JAXB, JAX-RS, JiBX, Velocity, or FreeMarker. A GWT version is also available. License: GNU Lesser General Public License (LGPL) Changes:
Better HTTP support (partial downloads, resumable uploads, or content integrity validation). Full support for WADL with automatic and always in sync documentation of REST APIs. A very complete implementation of JAX-RS 1.0. A new Restlet-GWT module. New extensions for JAXB 2.1, JiBX 1.1, Spring 2.5, OAuth, OSGi, Oracle XDB, and SSL. Improved support for Atom and APP. A new POP3 connector. A new Grizzly NIO HTTP server connector. A new internal HTTP client and server connectors. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
RT::Client::REST::Transaction(3pm)			User Contributed Perl Documentation			RT::Client::REST::Transaction(3pm)

NAME
RT::Client::REST::Transaction -- this object represents a transaction. SYNOPSIS
my $transactions = $ticket->transactions; my $count = $transactions->count; print "There are $count transactions. "; my $iterator = $transactions->get_iterator; while (my $tr = &$iterator) { print "Id: ", $tr->id, "; Type: ", $tr->type, " "; } DESCRIPTION
A transaction is a second-class citizen, as it does not exist (at least from the current REST protocol implementation) by itself. At the moment, it is always associated with a ticket (see parent_id attribute). Thus, you will rarely retrieve a transaction by itself; instead, you should use "transactions()" method of RT::Client::REST::Ticket object to get an iterator for all (or some) transactions for that ticket. ATTRIBUTES
id Numeric ID of the transaction. creator Username of the user who created the transaction. parent_id Numeric ID of the object the transaction is associated with. type Type of the transactions. Please referer to RT::Client::REST documentation for the list of transaction types you can expect this field to contain. Note that there may be some transaction types not (dis)covered yet. old_value Old value. new_value New value. field Name of the field the transaction is describing (if any). attachments I have never seen it set to anything yet. (I will some day investigate this). created Time when the transaction was created. content Actual content of the transaction. description Human-readable description of the transaction as provided by RT. data Not sure what this is yet. METHODS
RT::Client::REST::Transaction is a read-only object, so you cannot "store()" it. Also, because it is a second-class citizen, you cannot "search()" or "count()" it -- use "transactions()" method provided by RT::Client::REST::Ticket. retrieve To retrieve a transaction, attributes id and parent_id must be set. INTERNAL METHODS
rt_type Returns 'transaction'. SEE ALSO
RT::Client::REST, RT::Client::REST::Ticket, RT::Client::REST::SearchResult. AUTHOR
Dmitri Tikhonov <dtikhonov@yahoo.com> LICENSE
Perl license with the exception of RT::Client::REST, which is GPLed. perl v5.14.2 2011-12-27 RT::Client::REST::Transaction(3pm)