Examples of Response

  • com.jayway.restassured.response.Response
  • com.jcabi.http.Response
  • com.kurento.kmf.jsonrpcconnector.internal.message.Response
    Java representation for JSON media connector request. @author Ivan Gracia (igracia@gsyc.es) @version 1.0.0 @param < R>
  • com.lbslocal.test.helpers.Response
  • com.librato.metrics.HttpPoster.Response
  • com.linkedin.r2.message.Response
    @author Chris Pettitt @version $Revision$
  • com.logica.smpp.pdu.Response
  • com.mks.api.response.Response
  • com.mmoscene.h4j.communication.Response
  • com.ning.http.client.Response
    Represents the asynchronous HTTP response callback for an {@link com.ning.http.client.AsyncCompletionHandler}
  • com.opera.core.systems.scope.protos.UmsProtos.Response
  • com.proofpoint.http.client.Response
  • com.pugh.sockso.web.Response
  • com.restfb.WebRequestor.Response
  • com.rethinkdb.Ql2.Response
    Protobuf type {@code Response}
     You get back a response with the same [token] as your query. 
  • com.saya.response.Response
  • com.sosnoski.seismic.common.Response
  • com.squareup.okhttp.Response
  • com.sun.grizzly.tcp.Response
  • com.sun.mail.iap.Response
    This class represents a response obtained from the input stream of an IMAP server. @author John Mani
  • com.sun.research.wadl.x2006.x10.Response
    @opt nodefontname "Arial" @hidden
  • com.sun.research.ws.wadl.Response
    3.org/2001/XMLSchema}anyType"> <sequence> <element ref="{http://wadl.dev.java.net/2009/02}doc" maxOccurs="unbounded" minOccurs="0"/> <element ref="{http://wadl.dev.java.net/2009/02}param" maxOccurs="unbounded" minOccurs="0"/> <element ref="{http://wadl.dev.java.net/2009/02}representation" maxOccurs="unbounded" minOccurs="0"/> <any processContents='lax' namespace='##other' maxOccurs="unbounded" minOccurs="0"/> </sequence> <attribute name="status" type="{http://wadl.dev.java.net/2009/02}statusCodeList" /> <anyAttribute processContents='lax' namespace='##other'/> </restriction> </complexContent> </complexType>
  • com.sun.tools.ws.processor.model.Response
    @author WS Development Team
  • com.taobao.zeus.socket.protocol.Protocol.Response
  • com.twitter.finagle.httpx.Response
  • com.vmware.example.sqlfire.domain.Response
  • com.vtence.molecule.Response
  • com.xebia.cqrs.bus.Response
  • com.yourpackagename.framework.response.Response
    The purpose of this class is to contain the com.yourpackagename.framework.response that needs to be sent to the calling users @author Y Kamesh Rao
  • com.youtube.vitess.gorpc.Response
  • com.zaranux.os.server.core.Response
  • common.Response
  • de.anomic.crawler.retrieval.Response
  • de.javakaffee.web.msm.integration.TestUtils.Response
  • de.scoopgmbh.copper.Response
    Container for asynchronous responses. @author austermann @param < E>
  • dk.brics.jwig.Response
    Response for an HTTP request. The Response object holds the instantiated handlers as well as a payload of data that is sent to the client. Programmers can store data related to the computation of the response in the {@link #getRequestScopeMap} propertyof the Response
  • edu.cmu.cs.stage3.alice.core.Response
  • eu.planets_project.ifr.core.servreg.api.Response
    Service registry response type. @author Fabian Steeg (fabian.steeg@uni-koeln.de)
  • feign.Response
    An immutable response to an http invocation which only returns string content.
  • fi.iki.elonen.NanoHTTPD.Response
  • fitnesse.http.Response
  • foo.domaintest.action.Response
    A configurable HTTP response.
  • hamsam.api.Response
    A response to allow or disallow a user request. There are scenarios where the user is asked to allow or disallow a request that came from another user. Some examples are request to add a user to another user's buddy list, an invitation for conference, and request for file transfer. If they disallow such requests, they are requested to give an explanation why they chose to disallow the request. This class encapsulates the choice that the user made as well as the explanation they gave, if any. @author Raghu
  • io.airlift.http.client.Response
  • io.fabric8.etcd.api.Response
  • io.fabric8.gateway.handlers.detecting.protocol.openwire.command.Response
    @openwire :marshaller code="30" @version $Revision: 1.6 $
  • io.s4.message.Response
  • io.teknek.hiveunit.common.Response
    Contains Hive responses to certain executed statement
  • io.teknek.intravert.model.Response
  • javax.sip.message.Response
    etf.org/rfc/rfc3262.txt">RFC 3262. When the UAC creates a new request, it can insist on reliable delivery of provisional responses for that request. To do that, it inserts a Require header field with the option tag 100rel into the request. A Require header with the value 100rel MUST NOT be present in any requests excepting INVITE, although other extensions to SIP may allow its usage with other request methods. If the UAC does not wish to insist on usage of reliable provisional responses, but merely indicate that it supports them if the UAS needs to send one, a Supported header MUST be included in the request with the option tag 100rel. The UAC SHOULD include this in all INVITE requests.

    A UAS MAY send any non-100 provisional response to INVITE reliably, so long as the initial INVITE request (the request whose provisional response is being sent reliably) contained a Supported header field with the option tag 100rel. The provisional response to be sent reliably is constructed by the UAS and MUST contain a Require header field containing the option tag 100rel, and MUST include an RSeq header field. Retransmissions of the reliable provisional response cease when a matching PRACK is received by the UA core. PRACK is like any other request within a dialog, and is treated likewise. A matching PRACK is defined as one within the same dialog as the response, and whose method, CSeq-num, and RSeq-num in the RAck header field match, respectively, the method and sequence number from the CSeq and the sequence number from the RSeq of the reliable provisional response.

  • 2xx: Success -- the action was successfully received, understood, and accepted.
  • 3xx: Redirection -- further action needs to be taken in order to complete the request; 3xx responses give information about the user's new location, or about alternative services that might be able to satisfy the call.
  • 4xx: Client Error -- the request contains bad syntax or cannot be fulfilled at this server; 4xx responses are definite failure responses from a particular server. The client SHOULD NOT retry the same request without modification. However, the same request to a different server might be successful.
  • 5xx: Server Error -- the server failed to fulfill an apparently valid request; 5xx responses are failure responses given when a server itself has erred.
  • 6xx: Global Failure -- the request cannot be fulfilled at any server; 6xx responses indicate that a server has definitive information about a particular user, not just the particular instance indicated in the Request-URI. SIP status codes are extensible. The response codes are consistent with, and extend, HTTP/1.1 response codes. Not all HTTP/1.1 response codes are appropriate, and only those that are appropriate are given here. Other HTTP/1.1 response codes SHOULD NOT be used. Also, SIP defines a new class, 6xx.

    SIP applications are not required to understand the meaning of all registered response codes, though such understanding is obviously desirable. However, applications must understand the class of any status code, as indicated by the first digit and outlined above. Applications treat any unrecognized status code as being equivalent to the x00 status code of that class, with the exception that an unrecognized status code must not be cached. For example, if a client receives an unrecognized status code of 431, it can safely assume that there was something wrong with its request and treat the Response as if it had received a BAD_REQUEST(400) status code. In such cases, user agents should present to the user the message body returned with the Response, since that message body is likely to include human-readable information which will explain the unusual status.

    This specification supports the response codes defined in RFC3261 and also the response code extensions for the event notification framework and PUBLISH, documented in RFC3265 and RFC3909, these are highlighted in italic. Class status codes (x00, i.e. 100) are are highlighted in bold.

    Class Code
    PROVISIONAL (1xx)
  • TRYING - 100
  • RINGING - 180
  • CALL_IS_BEING_FORWARDED - 181
  • QUEUED - 182
  • SESSION_PROGRESS - 183
  • SUCCESS (2xx)
  • OK - 200
  • ACCEPTED - 202 (Extension RFC3265)
  • REDIRECTION (3xx)
  • MULTIPLE_CHOICES - 300
  • MOVED_PERMANENTLY - 301
  • MOVED_TEMPORARILY - 302
  • USE_PROXY - 305
  • ALTERNATIVE_SERVICE - 380
  • CLIENT_ERROR (4xx)
  • BAD_REQUEST - 400
  • UNAUTHORIZED - 401
  • PAYMENT_REQUIRED - 402
  • FORBIDDEN - 403
  • NOT_FOUND - 404
  • METHOD_NOT_ALLOWED - 405
  • NOT_ACCEPTABLE - 406
  • PROXY_AUTHENTICATION_REQUIRED - 407
  • REQUEST_TIMEOUT - 408
  • GONE - 410
  • CONDITIONAL_REQUEST_FAILED - 412 (Extension RFC3909)
  • REQUEST_ENTITY_TOO_LARGE - 413
  • REQUEST_URI_TOO_LONG - 414
  • UNSUPPORTED_MEDIA_TYPE - 415
  • UNSUPPORTED_URI_SCHEME - 416
  • BAD_EXTENSION - 420
  • EXTENSION_REQUIRED - 421
  • INTERVAL_TOO_BRIEF - 423
  • TEMPORARILY_UNAVAILABLE - 480
  • CALL_OR_TRANSACTION_DOES_NOT_EXIST - 481
  • LOOP_DETECTED - 482
  • TOO_MANY_HOPS - 483
  • ADDRESS_INCOMPLETE - 484
  • AMBIGUOUS - 485
  • BUSY_HERE - 486
  • REQUEST_TERMINATED - 487
  • NOT_ACCEPTABLE_HERE - 488
  • BAD EVENT - 489 (Extension RFC3265)
  • REQUEST_PENDING - 491
  • UNDECIPHERABLE - 493
  • SERVER_ERROR (5xx)
  • SERVER_INTERNAL_ERROR - 500
  • NOT_IMPLEMENTED - 501
  • BAD_GATEWAY - 502
  • SERVICE_UNAVAILABLE - 503
  • SERVER_TIMEOUT - 504
  • VERSION_NOT_SUPPORTED - 505
  • MESSAGE_TOO_LARGE - 513
  • GLOBAL_ERROR (6xx)
  • BUSY_EVERYWHERE - 600
  • DECLINE - 603
  • DOES_NOT_EXIST_ANYWHERE - 604
  • SESSION_NOT_ACCEPTABLE - 606
  • @author BEA Systems, NIST @version 1.2
  • javax.ws.rs.core.Response
    Defines the contract between a returned instance and the runtime when an application needs to provide meta-data to the runtime.

    An application class should not extend this class directly. {@code Response} class isreserved for an extension by a JAX-RS implementation providers. An application should use one of the static methods to create a {@code Response} instance using a ResponseBuilder.

    Several methods have parameters of type URI, {@link UriBuilder} providesconvenient methods to create such values as does {@link URI#create(java.lang.String)}.

    @author Paul Sandoz @author Marc Hadley @author Marek Potociar @see Response.ResponseBuilder @since 1.0
  • javax.xml.ws.Response
    The Response interface provides methods used to obtain the payload and context of a message sent in response to an operation invocation.

    For asynchronous operation invocations it provides additional methods to check the status of the request. The get(...) methods may throw the standard set of exceptions and their cause may be a RemoteException or a {@link WebServiceException} that represents the error that occured during theasynchronous method invocation.

    @since JAX-WS 2.0
  • jp.ameba.mongo.protocol.Response
    OP_REPLY に相当するメッセージ情報です。 @author suguru
  • juzu.Response
    xoplatform.org");

    Proceed to render phase

    A Response.View response instructs Juzu to proceed to the render phase of a valid view controller, this kind of response can be created using an {@link juzu.request.ActionContext}, however the best way is to use a controller companion class that carries method factories for creating render responses.

    Type safe {@link juzu.Response.View} factory method are generated for each view or resource controllermethods. The signature of an render factory is obtained by using the same signature of the controller method.

     public class MyController { @Action public  {@link juzu.Response.View} myAction() {return MyController_.myView("hello"); } @View public void myView(String param) { } } 

    Mime response

    Mime response are used by the {@link juzu.request.Phase#VIEW} and the {@link juzu.request.Phase#RESOURCE} phases.Both contains a content to be streamed to the client but still they have some noticeable differences.

    The {@link juzu.Response.Content} class is the base response class which will work well for the two phases.However the {@link juzu.request.Phase#VIEW} can specify an optional title and the {@link juzu.request.Phase#RESOURCE}can specify an optional status code for the user agent response.

    Responses are created using the {@link Response} factory methods such as

    Response can also created from {@link juzu.template.Template} directly:

     public class MyController { @Inject @Path("index.gtmpl")  {@link juzu.template.Template} index;@View public  {@link juzu.Response.Content} myView() {return index.ok(); } @Inject @Path("error.gtmpl")   {@link juzu.template.Template} error;@Resource public  {@link juzu.Response.Content} myView() {return error.notFound(); } } 

    The {@link juzu.template.Template.Builder} can also create responses:

     public class MyController { @Inject @Path("index.gtmpl") index index; @View public  {@link juzu.Response.Content} myView() {return index.with().label("hello").ok(); } } 
    @author Julien Viet
  • kanakata.analytics.Response
  • litmus.functional.Response
  • mongrel2.Response
    Generic response to send to Mongrel2. @author Karl Ostendorf
  • net.eldiosantos.command.commands.response.Response
    Class to hold the response lines and exceptions ocurreds during the execution process. @author Eldius
  • net.java.dev.wadl.x2009.x02.ResponseDocument.Response
  • net.noderunner.amazon.s3.Response
    The parent class of all other Responses.

    Returns status codes that should be checked.

  • net.pterodactylus.sone.freenet.fcp.Command.Response
  • net.pterodactylus.util.web.Response
  • net.sf.antcontrib.antserver.Response
    Place class description here. @author Matthew Inger
  • net.sourceforge.pebble.domain.Response
    Represents a response to a blog entry - either a comment or a TrackBack. @author Simon Brown
  • nexj.core.rpc.Response
    The object containing the server response.
  • nz.ac.massey.cs.deploymentpuzzlersurvey.Response
    A single reponse. @author jens dietrich
  • one.nio.http.Response
  • org.adoptopenjdk.jitwatch.ui.Dialogs.Response
  • org.agorava.api.rest.Response
    @author Antoine Sabot-Durand
  • org.apache.abdera.protocol.Response
  • org.apache.activemq.apollo.openwire.command.Response
    @openwire :marshaller code="30" @version $Revision: 1.6 $
  • org.apache.activemq.command.Response
    @openwire :marshaller code="30" @version $Revision: 1.6 $
  • org.apache.aurora.gen.Response
  • org.apache.catalina.Response
    A Response is the Catalina-internal facade for a ServletResponse that is to be produced, based on the processing of a corresponding Request. @author Craig R. McClanahan @version $Revision: 466595 $ $Date: 2006-10-21 23:24:41 +0100 (Sat, 21 Oct 2006) $
  • org.apache.catalina.connector.Response
    Wrapper object for the Coyote response. @author Remy Maucherat @author Craig R. McClanahan @version $Id: Response.java 964733 2010-07-16 10:26:09Z markt $
  • org.apache.chemistry.opencmis.client.bindings.spi.http.Response
    HTTP Response.
  • org.apache.cocoon.environment.Response
    Defines an interface to provide client response information . @author Davanum Srinivas @author Carsten Ziegeler @version CVS $Revision: 1.1.1.1.2.1 $ $Date: 2001/08/20 14:07:30 $
  • org.apache.coyote.Response
    Response object. @author James Duncan Davidson [duncan@eng.sun.com] @author Jason Hunter [jch@eng.sun.com] @author James Todd [gonzo@eng.sun.com] @author Harish Prabandham @author Hans Bergsten @author Remy Maucherat
  • org.apache.directory.api.ldap.model.message.Response
    Super interface used as a marker for all protocol response type messages. Note that only 2 response interfaces directly extend this interfaces. They are listed below:
    All other responses derive from the ResultResponse interface. These responses unlike the three above have an LdapResult component. The ResultResponse interface takes this into account providing a Response with an LdapResult property. @author Apache Directory Project
  • org.apache.directory.shared.ldap.model.message.Response
    Super interface used as a marker for all protocol response type messages. Note that only 2 response interfaces directly extend this interfaces. They are listed below:
    All other responses derive from the ResultResponse interface. These responses unlike the three above have an LdapResult component. The ResultResponse interface takes this into account providing a Response with an LdapResult property. @author Apache Directory Project
  • org.apache.drill.exec.rpc.Response
  • org.apache.geronimo.webservices.WebServiceContainer.Response
  • org.apache.hadoop.hbase.rest.client.Response
    The HTTP result code, response headers, and body of a HTTP response.
  • org.apache.hadoop.hbase.stargate.client.Response
    The HTTP result code, response headers, and body of a HTTP response.
  • org.apache.http.client.fluent.Response
  • org.apache.james.protocols.api.Response
    Protocol response to send to the client
  • org.apache.nutch.net.protocols.Response
    A response interface. Makes all protocols model HTTP.
  • org.apache.openejb.client.Response
  • org.apache.qpid.disttest.message.Response
  • org.apache.s4.message.Response
  • org.apache.soap.rpc.Response
    A Response object represents an RPC response. Both the client and the server use Response objects to represent the result of a method invocation. @author Matthew J. Duftler (duftler@us.ibm.com) @author Sanjiva Weerawarana (sanjiva@watson.ibm.com)
  • org.apache.tapestry.services.Response
    API agnostic wrapper for generating a response. Bridges the gaps between the Servlet API and the Portlet API.
  • org.apache.tapestry5.services.Response
    API agnostic wrapper for generating a response. Bridges the gaps between the Servlet API and the Portlet API.

    The Response service is a {@linkplain org.apache.tapestry5.ioc.services.PropertyShadowBuilder shadow} of the currentthread's response object.

  • org.apache.tomcat.core.Response
    @author James Duncan Davidson [duncan@eng.sun.com] @author Jason Hunter [jch@eng.sun.com] @author James Todd [gonzo@eng.sun.com] @author Harish Prabandham @author Hans Bergsten
  • org.apache.tuscany.sca.sample.comet.model.Response
  • org.apache.wicket.Response
    Abstract base class for different implementations of response writing. A subclass must implement write(String) to write a String to the response destination (whether it be a browser, a file, a test harness or some other place). A subclass may optionally implement close(), encodeURL(String), redirect(String), isRedirect() or setContentType(String) as appropriate. @author Jonathan Locke
  • org.apache.wicket.request.Response
    Abstract base class for different implementations of response writing.

    The implementation may not support calling both {@link #write(byte[])} and{@link #write(CharSequence)} on the same {@link Response} instance. @author Matej Knopp @author igor.vaynberg

  • org.apache.wink.webdav.model.Response
    The response XML element per the WebDAV specification [RFC 4918]
     Name:       response Namespace:  DAV: Purpose:    Holds a single response describing the effect of a method on resource and/or its properties. Description: A particular href MUST NOT appear more than once as the child of a response XML element under a multistatus XML element. This requirement is necessary in order to keep processing costs for a response to linear time.  Essentially, this prevents having to search in order to group together all the responses by href.  There are, however, no requirements regarding ordering based on href values. <!ELEMENT response (href, ((href*, status)|(propstat+)), responsedescription?) > 
  • org.ardverk.dht.storage.message.Response
  • org.asynchttpclient.Response
    Represents the asynchronous HTTP response callback for an {@link AsyncCompletionHandler}
  • org.brickred.socialauth.util.Response
    Encapsulates the HTTP status, headers and the content. @author tarunn@brickred.com
  • org.cast.cwm.data.Response
  • org.ch3ck3r.jgbx.responses.Response
    The base response class. @author Frank Zechert @version 1
  • org.dmd.dmp.server.extended.Response
  • org.doctester.testbrowser.Response
  • org.drools.guvnor.server.files.Response
  • org.drools.repository.remoteapi.Response
  • org.eclipse.jetty.client.api.Response

    {@link Response} represents a HTTP response and offers methods to retrieve status code, HTTP versionand headers.

    {@link Response} objects are passed as parameters to {@link Response.Listener} callbacks, or asfuture result of {@link Request#send()}.

    {@link Response} objects do not contain getters for the response content, because it may be too largeto fit into memory. The response content should be retrieved via {@link Response.Listener#onContent(Response,ByteBuffer) contentevents}, or via utility classes such as {@link BufferingResponseListener}.

  • org.eclipse.jetty.http.MetaData.Response
  • org.eclipse.jetty.server.Response

    {@link Response} provides the implementation for {@link HttpServletResponse}.

  • org.eclipse.webdav.http.client.Response
    An HTTP response message.

    Note: This class/interface is part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.

  • org.elasticsearch.hadoop.rest.Response
  • org.exolab.jms.net.connector.Response
    A Response wraps the result of a remote method invocation @author Tim Anderson @version $Revision: 1.1 $ $Date: 2004/11/26 01:51:03 $ @see Request @see Connection
  • org.exoplatform.services.remote.group.Response
    @author Tuan Nguyen (tuan08@users.sourceforge.net) @since Mar 4, 2005 @version $Id: Response.java 5799 2006-05-28 17:55:42Z geaz $
  • org.gatein.pc.test.unit.protocol.response.Response
    @author Julien Viet @version $Revision: 1.1 $
  • org.geoserver.ows.Response
    Response to an operation, which serializes the result of the operation to an output stream.

    A response must specify the following information:

    Optionally, a response may declare a well-known name for it. This well known name corresponds to the "outputFormat" parameter which is supported on many types of OWS request.

    @author Justin Deoliveira, The Open Planning Project, jdeolive@openplans.org
  • org.geotools.data.ows.Response
    Provides a base class for Responses from an OWS. Checks the incoming content for a ServiceException and parses it if it encounters one. @author rgould @source $URL$
  • org.glassfish.grizzly.http.server.Response
    Wrapper object for the Coyote response. @author Remy Maucherat @author Craig R. McClanahan @version $Revision: 1.2 $ $Date: 2006/11/02 20:01:44 $
  • org.hampelratte.svdrp.Response
  • org.hornetq.core.server.group.impl.Response
    A response to a proposal @author Andy Taylor
  • org.hpi.dialogue.protocol.response.Response
    @author Jean Villete
  • org.ibeans.api.Response
  • org.infinispan.remoting.responses.Response
    A response to be sent back to a remote caller @author Manik Surtani @since 4.0
  • org.jasig.cas.authentication.principal.Response
    Encapsulates a Response to send back for a particular service. @author Scott Battaglia @author Arnaud Lesueur @version $Revision: 1.1 $ $Date: 2005/08/19 18:27:17 $ @since 3.1
  • org.jboss.blacktie.jatmibroker.xatmi.Response
    This class encapsulates the response from the remote service and the return code
  • org.jboss.narayana.blacktie.jatmibroker.xatmi.Response
    This class encapsulates the response from the remote service and the return code
  • org.jboss.soa.esb.actions.soap.SOAPClient.Response
  • org.jboss.test.ws.jaxws.jbws1798.generated.GetCountryCodesResponse.Response
    3.org/2001/XMLSchema}anyType"> <sequence> </sequence> </restriction> </complexContent> </complexType>
  • org.jboss.test.ws.jaxws.jbws1843.generated.GetCountryCodesResponse.Response
    [JBWS-1843] WSDL with custom schema imports causes java.lang.OutOfMemoryError: Java heap space when there are circular schema imports dependencies @author richard.opalka@jboss.com @since Oct 10, 2007
  • org.jboss.test.ws.jaxws.jbws2009.generated.GetCountryCodesResponse.Response
    3.org/2001/XMLSchema}anyType"> <sequence> </sequence> </restriction> </complexContent> </complexType>
  • org.jgroups.blocks.Response
    A handback object shipped as a parameter to {@link AsyncRequestHandler#handle(org.jgroups.Message,Response)}. Encapsulates information needed to send a response, e.g. the request ID, the sender etc. @author Bela Ban @since 3.3
  • org.jinstagram.http.Response
    Represents an HTTP Response.
  • org.jredis.protocol.Response
    [TODO: detail the requirements - this is wip.]

    Response is a {@link Message} object that will read itself from a {@link InputStream} upon demand. It is provided by {@link Protocol}s as the result of a call to {@link Protocol#createResponse(Command)}. A Response is a generalize contract and does not provide the necessary semantics corresponding to the data for the various response possibilities (such as bulk data to a collection, value to bytes, etc.)

    This specification also does not specify whether a response object can be reused (to read the same command type response). This is left to the provider of the implementation. If a provider does NOT wish to re-use responses, they should raise a {@link ProviderException} in any subsequent calls to{@link Response#read(InputStream)}. This class, however, does not and will not provide a 'reset' means. / [TODO: document me!] @author Joubin Houshyar (alphazero@sensesay.net) @version alpha.0, 04/02/09 @since alpha.0

  • org.jsoup.Connection.Response
  • org.jwall.rbl.dns.Response
  • org.kairosdb.client.response.Response
    Response returned by the KairosDB server.
  • org.lightcouch.Response
  • org.mortbay.jetty.Response
    Response.

    Implements {@link javax.servlet.HttpServletResponse} from the {@link javax.servlet} package.

    @author gregw
  • org.nfctools.scio.Response
  • org.nutz.http.Response
  • org.objectweb.celtix.bindings.Response
  • org.olat.ims.qti.editor.beecom.objects.Response
    @author rkulow
  • org.opendope.questions.Response
    3.org/2001/XMLSchema}anyType"> <choice> <element name="free" minOccurs="0"> <complexType> <complexContent> <restriction base="{http://www.w3.org/2001/XMLSchema}anyType"> </restriction> </complexContent> </complexType> </element> <element name="fixed" minOccurs="0"> <complexType> <complexContent> <restriction base="{http://www.w3.org/2001/XMLSchema}anyType"> <sequence> <element name="item" maxOccurs="unbounded"> <complexType> <complexContent> <restriction base="{http://www.w3.org/2001/XMLSchema}anyType"> <sequence> <element name="label" type="{http://www.w3.org/2001/XMLSchema}string"/> <element name="value" type="{http://www.w3.org/2001/XMLSchema}string"/> </sequence> </restriction> </complexContent> </complexType> </element> </sequence> <attribute name="canSelectMany" type="{http://www.w3.org/2001/XMLSchema}boolean" /> </restriction> </complexContent> </complexType> </element> </choice> </restriction> </complexContent> </complexType>
  • org.openqa.selenium.remote.Response
  • org.opensaml.liberty.paos.Response
    Liberty Alliance PAOS Response header.
  • org.opensaml.saml1.core.Response
    This interface defines how the object representing a SAML1 Response element behaves.
  • org.opensaml.saml2.core.Response
    SAML 2.0 Core Response.
  • org.opensaml.saml2.ecp.Response
    SAML 2.0 ECP Response SOAP header.
  • org.opensocial.Response
    OpenSocial data response; encapsulates all information returned by a provider after processing a data request sent from a {@link Client}. @author Jason Cooper
  • org.openswing.swing.message.receive.java.Response
  • org.owasp.webscarab.model.Response
    Represents a HTTP response as sent by an HTTP server @author rdawes
  • org.raml.model.Response
  • org.restlet.Response
    Generic response sent by server connectors. It is then received by client connectors. Responses are uniform across all types of connectors, protocols and components. @see org.restlet.Request @see org.restlet.Uniform @author Jerome Louvel
  • org.restlet.client.Response
    Generic response sent by server connectors. It is then received by client connectors. Responses are uniform across all types of connectors, protocols and components. @see org.restlet.client.Request @see org.restlet.client.Uniform @author Jerome Louvel
  • org.restlet.data.Response
  • org.scribe.model.Response
    Represents an HTTP Response. @author Pablo Fernandez
  • org.sgx.yuigwt.yui.io.Response
    response object returned by io.send() @author sg
  • org.simpleframework.http.Response
    This is used to represent the HTTP response. This provides methods that can be used to set various characteristics of the response. An OutputStream can be acquired via this interface which can be used to write the response body. A buffer size can be specified when acquiring the output stream which allows data to be buffered until it over flows or is flushed explicitly. This buffering allows a partially written response body to be reset.

    This should never allow the message body be sent if it should not be sent with the headers as of RFC 2616 rules for the presence of a message body. A message body must not be included with a HEAD request or with a 304 or a 204 response. A proper implementation of this will prevent a message body being sent if the response is to a HEAD request of if there is a 304 or 204 response code.

    It is important to note that the Response controls the processing of the HTTP pipeline. The next HTTP request is not processed until the response has been sent. To ensure that the response is sent the close method of the response or the output stream should be used. This will notify the server to dispatch the next request in the pipeline for processing. @author Niall Gallagher

  • org.smpp.pdu.Response
    Represents a PDU response. All classes which are used as SMPP response are derived from this class. @author Logica Mobile Networks SMPP Open Source Team @version $Revision: 1.1 $
  • org.sonar.api.server.ws.Response
    HTTP response @since 4.2
  • org.sonatype.nexus.extdirect.model.Response
    Ext.Direct response. @since 3.0
  • org.subethamail.smtp.client.SMTPClient.Response
  • org.syncany.operations.daemon.messages.api.Response
  • org.tarantool.core.cmd.Response
    Tarantool server response @author dgreen @version $Id: $
  • org.vfny.geoserver.Response
    The Response interface serves as a common denominator for all service operations that generates content.

    The work flow for this kind of objects is divided in two parts: the first is executing a request and the second writing the result to an OuputStream.

    1. Execute: execute(Request)
      • Executing the request means taking a Request object and, based on it's set of request parameters, do any heavy processing necessary to produce the response.
      • Once the execution has been made, the Response object should be ready to send the response content to an output stream with minimal risk of generating an exception.
      • Anyway, it is not required, even recomended, that the execution process generates the response content itself; just that it performs any query or processing that should generate a trapable error.
      • Execute may throw a ServiceException if they wish to supply a specific response in error. As an example the WFSTransaction process has a defined Transaction Document with provisions for reporting error information.
    2. ContentType: getContentType()
      • Called to set the response type. Depending on the stratagy used by AbstractService the framework may be commited to returning this type.
    3. Writing: writeTo(OutputStream)
      • Write the response to the provided output stream.
      • Any exceptions thrown by this writeTo method may never reach the end user in useable form. You should assume you are writing directly to the client.

    Note: abort() will be called as part of error handling giving your response subclass a chance to clean up any temporary resources it may have required in execute() for use in writeTo().

    This is specially usefull for streamed responses such as wfs GetFeature or WMS GetMap, where the execution process can be used to parse parameters, execute queries upon the corresponding data sources and leave things ready to generate a streamed response when the consumer calls writeTo.

    @author Gabriel Rold?n @version $Id: Response.java 11475 2009-02-28 18:41:23Z jdeolive $
  • org.voltdb.TestJSONInterface.Response
  • org.wiztools.restclient.Response
    @author subwiz
  • org.wiztools.restclient.bean.Response
    @author subwiz
  • org.wymiwyg.rwcf.Response
    @author reto
  • org.wymiwyg.wrhapi.Response
  • org.xrace.desjardins.reponse.Response
    Class Response. @version $Revision$ $Date$
  • org.yaac.shared.egql.Response
    not like Result, Response will be returned immediately so that client side can initialize result panels based on response content @author Max Zhu (thebbsky@gmail.com)
  • play.mvc.Http.Response
  • protocol.Response
    A general representation of a response @author Yury Michurin
  • pt.opensoft.msg.Response
    @author Luis Pereira @version 1.0
  • ratpack.http.Response
    A response to a request.

    The headers and status are configured, before committing the response with one of the {@link #send} methods.

  • reddit.json.Response
    Created by tama on 6/25/14.
  • redis.clients.jedis.Response
  • retrofit.client.Response
  • sample.model.Response
  • scrumdo.transport.Response
    @author Soren
  • se.bitcraze.crazyflie.crtp.Crtp.Response
  • spark.Response
    Provides functionality for modifying the response @author Per Wendel
  • twitter4j.http.Response
    A data class representing HTTP Response @author Yusuke Yamamoto - yusuke at mac.com
  • unibg.overencrypt.protocol.Response
    Manages the response at client-side. @author Flavio Giovarruscio & Riccardo Tribbia @version 1.0
  • ve.net.dcs.sc.component.Response
    .ve @author Saul Pina - spina@dcs.net.ve @see Request @see Client
  • weibo4j.http.Response
    A data class representing HTTP Response @author Yusuke Yamamoto - yusuke at mac.com
  • yalp.mvc.Http.Response

  • Examples of org.geoserver.ows.Response

            // prepare the fake operation we're providing to the source output format
            final Operation sourceOperation = buildSourceOperation(operation, info);

            // lookup the operation we are going to use
            final Response sourceResponse = findSourceResponse(sourceOperation, info);
            if (sourceResponse == null) {
                throw new WFSException(
                        "Could not locate a response that can generate the desired source format '"
                                + info.getSourceFormat() + "' for transformation '" + info.getName() + "'");

            }

            // prepare the stream connections, so that we can do the transformation on the fly
            PipedInputStream pis = new PipedInputStream();
            final PipedOutputStream pos = new PipedOutputStream(pis);

            // submit the source output format execution, tracking exceptions
            Future<Void> future = executor.submit(new Callable<Void>() {

                @Override
                public Void call() throws Exception {
                    try {
                        sourceResponse.write(featureCollection, pos, sourceOperation);
                    } finally {
                        // close the stream to make sure the transformation won't keep on waiting
                        pos.close();
                    }
    View Full Code Here

    Examples of org.geotools.data.ows.Response

                super(url, null);
                this.url = url;
            }
            public Response createResponse( HTTPResponse response ) throws ServiceException,
                    IOException {
                return new Response(response){
                };
            }
    View Full Code Here

    Examples of org.glassfish.grizzly.http.server.Response


        public static void handleSendFile(final Request request) {
            final Object f = request.getAttribute(Request.SEND_FILE_ATTR);
            if (f != null) {
                final Response response = request.getResponse();
                if (response.isCommitted()) {
                    if (LOGGER.isLoggable(Level.WARNING)) {
                        LOGGER.log(Level.WARNING,
                                LogMessages.WARNING_GRIZZLY_HTTP_SERVER_REQUESTUTILS_SENDFILE_FAILED());
                    }

                    return;
                }

                final File file = (File) f;
                Long offset = (Long) request.getAttribute(Request.SEND_FILE_START_OFFSET_ATTR);
                Long len = (Long) request.getAttribute(Request.SEND_FILE_WRITE_LEN_ATTR);
                if (offset == null) {
                    offset = 0L;
                }
                if (len == null) {
                    len = file.length();
                }
                // let the sendfile() method suspend/resume the response.
                response.getOutputBuffer().sendfile(file, offset, len, null);
            }
        }
    View Full Code Here

    Examples of org.hampelratte.svdrp.Response

       * @param cmd
       *            The SVDRP command to send
       * @return The SVDRP response or null, if the Command couldn't be sent
       */
      public Response send(final Command cmd) {
        Response res = null;
        Connection connection=null;
        try {
          logger.trace("New connection");
          connection = new Connection(mIp, mPort, timeout, charset);
          logger.debug("Try to send VDR command: {}", cmd.getCommand());

          res = connection.send(cmd);
          logger.debug("Recived Message from VDR: {}", res.getMessage());
        } catch (Exception e) {
          logger.error("Could not connect to VDR on {}: {}", mIp + ":" + mPort,
              e);
        } finally {
          if (connection != null) {
    View Full Code Here

    Examples of org.hornetq.core.server.group.impl.Response

             SimpleString val = message.getSimpleStringProperty(ManagementHelper.HDR_PROPOSAL_VALUE);

             Integer hops = message.getIntProperty(ManagementHelper.HDR_DISTANCE);

             Response response = server.getGroupingHandler().receive(new Proposal(type, val), hops + 1);

             if (response != null)
             {
                server.getGroupingHandler().send(response, 0);
             }
    View Full Code Here

    Examples of org.hpi.dialogue.protocol.response.Response

                this.getWriter().flush();

                // initiating the reader and reading the response from the server
                this.setReader(this.getSocket().openInputStream());
                String serverMessage = this.readMessage();
                Response response = (Response) HPIDialogueProtocol.parseMessage(serverMessage);

                // closing the connections
                this.closeSocket();

                // return the retrieved response
    View Full Code Here

    Examples of org.ibeans.api.Response

            }

            Map<String, Object> props = new HashMap<String, Object>();
            props.put(HttpConstants.HEADER_CONTENT_TYPE, (ctx.getInvocationReturnType()==null ?
                        ctx.getReturnType().getMimeType() : ctx.getInvocationReturnType().getMimeType()));
            Response response = (result instanceof Response ? (Response)result : plugin.createResponse(result, props, null));

            //Now handled in the test case
            if (callback != null)
            {
                try
    View Full Code Here

    Examples of org.infinispan.remoting.responses.Response

          ClusteredGetCommand clusteredGetCommand = new ClusteredGetCommand(key, cache.getName());
          List<Response> response = doRemoteCall(clusteredGetCommand);
          if (response.isEmpty()) return null;
          if (response.size() > 1)
             throw new CacheLoaderException("Response length is always 0 or 1, received: " + response);
          Response firstResponse = response.get(0);
          if (firstResponse.isSuccessful() && firstResponse instanceof SuccessfulResponse) {
             return (InternalCacheEntry) ((SuccessfulResponse) firstResponse).getResponseValue();
          }

          String message = "Unknown response from remote cache: " + response;
          log.error(message);
    View Full Code Here

    Examples of org.jasig.cas.authentication.principal.Response

           
            this.openIdService = OpenIdService.createServiceFrom(request);
        }
       
        public void testGetResponse() {
            final Response response = this.openIdService.getResponse("test");
           
            assertNotNull(response);
           
            assertEquals("test", response.getAttributes().get("openid.assoc_handle"));
            assertEquals("http://www.ja-sig.org/?service=fa", response.getAttributes().get("openid.return_to"));
            assertEquals("http://openid.ja-sig.org/battags", response.getAttributes().get("openid.identity"));
           
            final Response response2 = this.openIdService.getResponse(null);
            assertEquals("cancel", response2.getAttributes().get("openid.mode"));
        }
    View Full Code Here

    Examples of org.jboss.blacktie.jatmibroker.xatmi.Response

            log.debug("service_request tx same as current");
          }

          Buffer request = requestMessage.getBuffer();
          log.debug("service_request tpcall");
          Response response = connection.tpcall(serviceName, request,
              noTimeout ? Connection.TPNOTIME : 0);
          responseMessage = new JABMessage(response);
          log.debug("service_request responsed");
        } catch (Exception e) {
          log.warn("service_request exception: " + e.getMessage());
    View Full Code Here
    TOP
    Copyright © 2018 www.massapi.com. All rights reserved.
    All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.