-
Control.Message
A {@link Message} with a text, time, travel status and information on the chat partner.
@author Sebastian
-
agentj.examples.udprouting.Message
This class represents a message (both HELLO and TC/LSA messages)
@author Ulrich Herberg
-
aleph.Message
The base class for aleph messages. When a PE receives a message m
, it executes that message's run()
method. Messages between pairs of PEs are received and executed in FIFO order: if PE0
sends m0
and then m1
to PE1
, then PE1
runs m0.run()
to completion befor starting m1.run()
. A message's run()
method should therefore not block for non-trivial durations. If you need to block, use aleph.AsynchMessage
. Messages from different PEs are not synchronized: if PE0
sends m0
and PE1
sends m1
to PE2
, then m0.run()
and m1.run()
may be run concurrently.
@see aleph.AsynchMessage
@author Maurice Herlihy
@date July 1998
-
android.os.Message
-
api.Message
-
ass3.program.core.message.Message
-
at.molindo.notify.model.Message
-
at.riemers.zero.base.controller.Message
@author tobias
-
biz.massivedynamics.modger.message.Message
A {@link Message} class that encapsulates a {@link String} and {@link MessageType}
@author Cruz Bishop
@since 1.0.0.0
-
br.com.caelum.vraptor.validator.Message
-
br.gov.frameworkdemoiselle.message.Message
Represents the configuration of a single message.
@author SERPRO
-
ca.uhn.hl7v2.model.Message
Represents a complete HL7 message including all structures, segments, and fields.
Note this it is not recommended to implement this interface directly, as it is subject to change. Instead, extend abstract implementations for your model classes, such as {@link AbstractMessage} and {@link AbstractGroup}
@author Bryan Tripp (bryan_tripp@sourceforge.net)
-
ch.njol.skript.localization.Message
Basic class to get text from the language file(s).
@author Peter Güttinger
-
ch.softappeal.yass.core.remote.Message
Common base class for remote requests and replies.
-
ch.usi.dslab.bezerra.netwrapper.Message
-
chatbot.client.Message
-
chrriis.dj.nativeswing.swtimpl.Message
The superclass of all the messages that are exchanged at the native interface.
@author Christopher Deckers
-
classes.Message
-
client.model.Message
@author immortal
-
client.model.utils.Message
@author Bernard , Romain
-
client.net.sf.saxon.ce.expr.instruct.Message
An xsl:message element in the stylesheet.
-
clueless.messaging.Message
Message base class
@author Chris
-
cn.com.neo.acceptor.Message
-
cn.edu.hfut.dmic.webcollector.handler.Message
消息
@author hu
-
cn.edu.pku.dr.requirement.elicitation.data.Message
-
co.paralleluniverse.galaxy.core.Message
@author pron
-
com.adito.notification.Message
Encapsulate a single message that is delivered by the {@link Notifier}to one or more {@link MessageSink} implementations.
A message must have a least one {@link Recipient}.
A message may be marked as Urgent in which case it is placed at the top of the queue.
-
com.aelitis.azureus.core.peermanager.messaging.Message
Basic peer message. A message is uniquely identified by the combination of ID and version.
-
com.agiletec.plugins.jpwebdynamicform.aps.system.services.message.model.Message
Implementation of an entity for a Messaging interaction. The elements of the 'message' entity, as declared in the configuration item, is build invoking the addAttribute() method, but this is allowed only during service initialization - in all the remaining cases this class must be instantiated invoking the associated service, which will get it cloning the prototype previously build.
@author M.Minnai, E.Mezzano
-
com.alibaba.ons.api.Message
消息类
-
com.alibaba.otter.canal.protocol.Message
@author zebin.xuzb @ 2012-6-19
@version 1.0.0
-
com.alibaba.otter.node.etl.select.selector.Message
数据对象
@author jianghang 2012-7-31 下午02:43:08
-
com.alibaba.rocketmq.common.message.Message
消息,Producer与Consumer使用
@author shijia.wxr
@since 2013-7-18
-
com.aliyun.openservices.ons.api.Message
消息类
-
com.almende.eve.entity.Message
-
com.amazonaws.services.kinesis.multilang.messages.Message
Abstract class for all messages that are sent to the client's process.
-
com.amazonaws.services.simpleemail.model.Message
Represents the message to be sent, composed of a subject and a body.
-
com.amazonaws.services.sqs.model.Message
-
com.android.tools.idea.gradle.messages.Message
-
com.apigee.flow.message.Message
-
com.apress.prospring3.springblog.web.form.Message
@author Clarence
-
com.art.anette.datamodel.dataobjects.simple.Message
Die Klasse beschreibt Chat-Nachrichten die zwischen den Clients ausgetauscht werden.
@author Alexander von Bremen-Kühne
-
com.ateam.webstore.model.Message
@author Hendrix Tavarez
-
com.avaje.ebeaninternal.server.cluster.mcast.Message
-
com.bloomberglp.blpapi.Message
-
com.brewtab.irc.messages.Message
lp.org/irchelp/rfc/rfc.html">
http://www.irchelp.org/irchelp/rfc/rfc.html
-
com.calclab.emite.core.client.xmpp.stanzas.Message
-
com.calclab.emite.core.stanzas.Message
g/rfcs/rfc6121.html#message-syntax">RFC 6121 - Section 5.2
-
com.caucho.bam.packet.Message
Unidirectional message with a value.
-
com.caucho.hemp.packet.Message
Unidirectional message with a value.
-
com.cellasoft.jchat.utils.Message
Classe utilizzata usata per gestire i messaggi di chat.
@author Davide Vallicella
@author Nicola Aldà
@version 1.0
-
com.changestuffs.server.persistence.beans.Message
-
com.coherentlogic.fred.client.core.domain.Message
ouisfed.org/docs/fred/series_observations.html">
series_observations
@TODO Should this be an entity?
@author
Support
-
com.coherentlogic.wb.client.core.domain.Message
orldbank.org">
The provided parameter value is not valid
@todo Should this be serializable?
@author
Support
-
com.consol.citrus.message.Message
@author Christoph Deppisch
@since 2.0
-
com.cosmo.comm.Message
Representa un mensage gen�rico (puede ser de correo electr�nico, SMS, etc.).
NOTA: Lea atentamente las intrucciones de cada proveedor de comunicaciones para saber que campos son reconocidos por los distintos servidores de comunicaciones.
@author Gerard Llort
-
com.ctlok.springframework.web.servlet.view.rythm.tag.Message
@author Lawrence Cheung
-
com.dianping.cat.consumer.state.model.entity.Message
-
com.dianping.cat.message.Message
Message represents data collected during application runtime. It will be sent to back-end system asynchronous for further processing.
Super interface of Event
, Heartbeat
and Transaction
.
@see Event, Heartbeat, Transaction
@author Frankie Wu
-
com.digitaldan.jomnilinkII.Message
-
com.dotcms.repackage.org.jgroups.Message
-
com.dotcms.repackage.org.xbill.DNS.Message
-
com.dragome.model.interfaces.Message
Created by IntelliJ IDEA. User: andrew Date: Aug 5, 2009 Time: 11:45:21 AM To change this template use File | Settings | File Templates.
-
com.dtikhonov.model.Message
Created by dtikhonov on 08/05/14.
-
com.dyuproject.protostuff.parser.Message
Represents the message defined in the {@link Proto}.
@author David Yu
@created Dec 19, 2009
-
com.elasticinbox.core.model.Message
org/html/rfc3501#section-6.4.5">RFC3501
-
com.enioka.jqm.jpamodel.Message
Not part of any API - this an internal JQM class and may change without notice.
JPA persistence class for storing short messages that can be created by user code to inform users or systems of its progress. Often, a {@link Message} is created for each big step inside the user code.
This is an archive created from a {@link MessageJi} at the end of a {@link JobInstance} run (just before the {@link JobInstance} isdestroyed).
-
com.ettrema.mail.Message
@author brad
-
com.excilys.ebi.bank.web.messages.Message
-
com.exedosoft.plat.agent.Message
-
com.floreysoft.jmte.message.Message
-
com.flowpowered.networking.Message
-
com.freewebsys.sns.pojo.Message
-
com.fs.pxe.sfwk.spi.Message
-
com.getit.todoapp.service.Message
-
com.github.theholywaffle.teamspeak3.api.wrapper.Message
-
com.google.android.gcm.server.Message
GCM message.
Instances of this class are immutable and should be created using a {@link Builder}. Examples: Simplest message:
Message message = new Message.Builder().build();
Message with optional attributes: Message message = new Message.Builder() .collapseKey(collapseKey) .timeToLive(3) .delayWhileIdle(true) .build();
Message with optional attributes and payload data: Message message = new Message.Builder() .collapseKey(collapseKey) .timeToLive(3) .delayWhileIdle(true) .addData("key1", "value1") .addData("key2", "value2") .build();
-
com.google.api.services.gmail.model.Message
-
com.google.appengine.api.mail.MailService.Message
-
com.google.appengine.api.xmpp.Message
-
com.google.caja.reporting.Message
A Message that can be displayed to the user.
Messages can be formatted for immediate display to the user, or can be fed to another tool, such as an documentation or metadata generator, that might use then produce derived files.
@author mikesamuel@gmail.com
-
com.google.code.http4j.Message
-
com.google.code.lightssh.project.message.entity.Message
消息
@author Aspen
-
com.google.collide.client.util.WindowUnloadingController.Message
-
com.google.eclipse.protobuf.protobuf.Message
-
com.google.gwt.chrome.crx.client.Port.Message
-
com.google.gwt.dev.shell.remoteui.RemoteMessageProto.Message
-
com.google.gwt.i18n.server.Message
Describes a single translatable message.
-
com.google.inject.spi.Message
A message. Contains a source pointing to the code which resulted in this message and a text message.
@author crazybob@google.com (Bob Lee)
-
com.google.protobuf.Message
Abstract interface implemented by Protocol Message objects.
@author kenton@google.com Kenton Varda
-
com.google.sitebricks.i18n.Message
-
com.google.sitebricks.mail.imap.Message
Represents a complete IMAP message with all body parts materialized and decoded as appropriate (for example, non-UTF8 encodings are re-encoded into UTF8 for raw and rich text).
@author dhanji@gmail.com (Dhanji R. Prasanna)
-
com.google.transconsole.common.messages.Message
Value class for creating a Translation Console message, and displaying it in various forms (including XML suitable for inclusion in an XMB).
-
com.group5.jfs.Message
-
com.gwtplatform.carstore.client.application.widget.message.Message
-
com.hazelcast.core.Message
Message for {@link ITopic}.
@param < E> message type
-
com.impetus.labs.korus.core.message.Message
Message to be passed between the process contains ('KEY','VALUE') pairs.
-
com.infiniteautomation.rq.Message
-
com.jms.client.entity.Message
-
com.k42b3.neodym.Message
rg/licenses/gpl.html GPLv3
@link http://code.google.com/p/delta-quadrant
@version $Revision: 221 $
-
com.kyleduo.icomet.message.Message
-
com.liferay.portal.kernel.messaging.Message
-
com.linkedin.data.message.Message
Used to provide an error status and formattable message. {@link Message}s may be emitted as part of validating a Data object against a {@link com.linkedin.data.schema.DataSchema} or applyingpatches.
-
com.linkedin.helix.model.Message
Message class basically extends ZNRecord but provides additional fields
@author kgopalak
-
com.linkedin.r2.message.Message
An object that represents a message, either REST or RPC, and either request or response.
Messages are immutable and thread-safe. It is possible to clone an existing Message, modify details in the copy, and create a new Message instance that has the concrete type of the original message (REST/RPC, request/response) using the {@link #builder()} method.
@see com.linkedin.r2.message.rest.RestRequest
@see com.linkedin.r2.message.rest.RestResponse
@see com.linkedin.r2.message.rpc.RpcRequest
@see com.linkedin.r2.message.rpc.RpcResponse
@author Chris Pettitt
@version $Revision$
-
com.linkedin.restli.examples.greetings.api.Message
-
com.metadot.book.connectr.shared.messages.Message
-
com.netflix.astyanax.recipes.queue.Message
-
com.netflix.suro.message.Message
-
com.openshift.client.Message
@author Andre Dietisheim
-
com.oracle.truffle.r.runtime.RError.Message
-
com.pinterest.secor.message.Message
Message represents a raw Kafka log message.
@author Pawel Garbacki (pawel@pinterest.com)
-
com.python.pydev.analysis.messages.Message
-
com.qq.weixin.sdk.message.Message
all message parent is Message!
@author hujiawei
-
com.rabbitmq.messagepatterns.unicast.Message
-
com.redhat.ceylon.compiler.typechecker.tree.Message
-
com.sahuaro.domain.Message
-
com.sample.DroolsTest.Message
-
com.scooterframework.common.util.Message
Message represents a general purpose message.
@author (Fei) John Chen
-
com.sishuok.es.personal.message.entity.Message
系统消息 1、收件箱和发件箱内的消息默认365天后被放入垃圾箱 2、垃圾箱内的消息30天后自动物理删除 3、垃圾箱内的消息只有只有当收件人和发件人 把消息都从垃圾箱中删除后才能物理删除 4、收藏箱的不能删除
如果type==system_message_all表示是发给所有人的消息 策略如下: 1、首先在展示时(第一页),会会自动查所有的system_message_all 2、如果用户阅读了,直接复制一份 放入它的收件箱 状态改为system_message
如果消息是草稿 那么收件人状态是null
User: Zhang Kaitao
Date: 13-5-22 下午1:51
Version: 1.0
-
com.sissi.protocol.message.Message
@author kim 2013-10-27
-
com.sivalabs.springmvc.entities.Message
@author Siva
-
com.sivalabs.ssdemo.entities.Message
@author Siva
-
com.sleepycat.je.rep.utilint.BinaryProtocol.Message
-
com.springsource.greenhouse.utils.Message
A message to display to the user. Has a type indicating the kind of message.
@author Keith Donald
-
com.stepan.domain.Message
@author StepanThis class represents a single message object.
-
com.sun.corba.se.impl.protocol.giopmsgheaders.Message
This is the base interface for different message type interfaces.
@author Ram Jeyaraman 05/14/2000
-
com.sun.enterprise.ee.server.group.Message
Message is little more that what is needed for deployment.
@author haritham
-
com.sun.jersey.samples.jersey_ejb.entities.Message
@author pavel.bucek@sun.com
-
com.sun.jini.tool.envcheck.Reporter.Message
-
com.sun.star.lib.uno.environments.remote.Message
A remote request or reply message.
-
com.sun.tck.wma.Message
This the base interface for derived interfaces that represent various types of messages. This package is designed to work with
Message
objects that may contain different elements depending on the underlying messaging protocol. This is different from
Datagram
s that are assumed always to be just blocks of binary data. An adapter specification for a given messaging protocol may define further interfaces derived from the
Message
interfaces included in this generic specification.
The wireless messaging protocols that are accessed via this API are typically of store-and-forward nature, unlike network layer datagrams. Thus, the messages will usually reach the recipient, even if the recipient is not connected at the time of sending the message. This may happen a significant time later if the recipient is disconnected for a long time. Sending, and possibly also receiving, these wireless messages, typically involves a financial cost to the end user that cannot be neglected. Therefore, applications should not send many messages unnecessarily.
This interface contains the functionality common to all messages. Concrete object instances representing a message will typically implement other (sub)interfaces providing access to the content and other information in the message which is dependent on the type of the message.
Object instances implementing this interface are just containers for the data that is passed in. The setAddress()
method just sets the value of the address in the data container without any checking whether the value is valid in any way.
-
com.sun.tools.internal.ws.wsdl.document.Message
Entity corresponding to the "message" WSDL element.
@author WS Development Team
-
com.sun.tools.ws.wsdl.document.Message
Entity corresponding to the "message" WSDL element.
@author WS Development Team
-
com.sun.xml.internal.ws.api.message.Message
Represents a SOAP message.
What is a message?
A {@link Message} consists of the following:
- Random-accessible list of headers. a header is a representation of an element inside <soap:Header>. It can be read multiple times, can be added or removed, but it is not modifiable. See {@link HeaderList} for more about headers.
- The payload of the message, which is a representation of an element inside <soap:Body>. the payload is streamed, and therefore it can be only read once (or can be only written to something once.) once a payload is used, a message is said to be consumed. A message {@link #hasPayload() may not have any payload.}
- Attachments. TODO: can attachments be streamed? I suspect so. does anyone need to read attachment twice?
How does this abstraction work?
The basic idea behind the {@link Message} is to hide the actualdata representation. For example, a {@link Message} might beconstructed on top of an {@link InputStream} from the accepted HTTP connection,or it might be constructed on top of a JAXB object as a result of the method invocation through {@link Proxy}. There will be a {@link Message} implementation for each of those cases.
This interface provides a lot of methods that access the payload in many different forms, and implementations can implement those methods in the best possible way.
A particular attention is paid to make sure that a {@link Message}object can be constructed on a stream that is not fully read yet. We believe this improves the turn-around time on the server side.
It is often useful to wrap a {@link Message} into another {@link Message}, for example to encrypt the body, or to verify the signature as the body is read.
This representation is also used for a REST-ful XML message. In such case we'll construct a {@link Message} with emptyattachments and headers, and when serializing all headers and attachments will be ignored.
Message and XOP
XOP is considered as an {@link Codec}, and therefore when you are looking at {@link Message}, you'll never see <xop:Include> or any such elements (instead you'll see the base64 data inlined.) If a consumer of infoset isn't interested in handling XOP by himself, this allows him to work with XOP correctly even without noticing it.
For producers and consumers that are interested in accessing the binary data more efficiently, they can use {@link XMLStreamReaderEx} and{@link XMLStreamWriterEx}.
Message lifespan
Often {@link Packet} include information local to a particularinvocaion (such as {@code HttpServletRequest}, from this angle, it makes sense to tie a lifespan of a message to one pipeline invocation.
On the other hand, if you think about WS-RM, it often needs to hold on to a message longer than a pipeline invocation (you might get an HTTP request, get a message X, get a second HTTP request, get another message Y, and only then you might want to process X.)
TODO: what do we do about this?
TODO: can body element have foreign attributes? maybe ID for security? Yes, when the SOAP body is signed there will be an ID attribute present But in this case any security based impl may need access to the concrete representation. TODO: HTTP headers? Yes. Abstracted as transport-based properties. TODO: who handles SOAP 1.1 and SOAP 1.2 difference? As separate channel implementations responsible for the creation of the message? TODO: session? TODO: Do we need to expose SOAPMessage explicitly? SOAPMessage could be the concrete representation but is it necessary to transform between different concrete representations? Perhaps this comes down to how use channels for creation and processing. TODO: Do we need to distinguish better between creation and processing? Do we really need the requirement that a created message can be resused for processing. Shall we bifurcate? TODO: SOAP version issue SOAP version is determined by the context, so message itself doesn't carry it around (?) TODO: wrapping message needs easier. in particular properties and attachments.
@author Kohsuke Kawaguchi
-
com.sun.xml.internal.ws.wsdl.writer.document.Message
@author WS Development Team
-
com.sun.xml.ws.api.message.Message
Represents a SOAP message.
What is a message?
A {@link Message} consists of the following:
- Random-accessible list of headers. a header is a representation of an element inside <soap:Header>. It can be read multiple times, can be added or removed, but it is not modifiable. See {@link HeaderList} for more about headers.
- The payload of the message, which is a representation of an element inside <soap:Body>. the payload is streamed, and therefore it can be only read once (or can be only written to something once.) once a payload is used, a message is said to be consumed. A message {@link #hasPayload() may not have any payload.}
- Attachments. TODO: can attachments be streamed? I suspect so. does anyone need to read attachment twice?
How does this abstraction work?
The basic idea behind the {@link Message} is to hide the actualdata representation. For example, a {@link Message} might beconstructed on top of an {@link InputStream} from the accepted HTTP connection,or it might be constructed on top of a JAXB object as a result of the method invocation through {@link Proxy}. There will be a {@link Message} implementation for each of those cases.
This interface provides a lot of methods that access the payload in many different forms, and implementations can implement those methods in the best possible way.
A particular attention is paid to make sure that a {@link Message}object can be constructed on a stream that is not fully read yet. We believe this improves the turn-around time on the server side.
It is often useful to wrap a {@link Message} into another {@link Message}, for example to encrypt the body, or to verify the signature as the body is read.
This representation is also used for a REST-ful XML message. In such case we'll construct a {@link Message} with emptyattachments and headers, and when serializing all headers and attachments will be ignored.
Message and XOP
XOP is considered as an {@link Codec}, and therefore when you are looking at {@link Message}, you'll never see <xop:Include> or any such elements (instead you'll see the base64 data inlined.) If a consumer of infoset isn't interested in handling XOP by himself, this allows him to work with XOP correctly even without noticing it.
For producers and consumers that are interested in accessing the binary data more efficiently, they can use {@link XMLStreamReaderEx} and{@link XMLStreamWriterEx}.
Message lifespan
Often {@link Packet} include information local to a particularinvocaion (such as {@code HttpServletRequest}, from this angle, it makes sense to tie a lifespan of a message to one pipeline invocation.
On the other hand, if you think about WS-RM, it often needs to hold on to a message longer than a pipeline invocation (you might get an HTTP request, get a message X, get a second HTTP request, get another message Y, and only then you might want to process X.)
TODO: what do we do about this?
TODO: can body element have foreign attributes? maybe ID for security? Yes, when the SOAP body is signed there will be an ID attribute present But in this case any security based impl may need access to the concrete representation. TODO: HTTP headers? Yes. Abstracted as transport-based properties. TODO: who handles SOAP 1.1 and SOAP 1.2 difference? As separate channel implementations responsible for the creation of the message? TODO: session? TODO: Do we need to expose SOAPMessage explicitly? SOAPMessage could be the concrete representation but is it necessary to transform between different concrete representations? Perhaps this comes down to how use channels for creation and processing. TODO: Do we need to distinguish better between creation and processing? Do we really need the requirement that a created message can be resused for processing. Shall we bifurcate? TODO: SOAP version issue SOAP version is determined by the context, so message itself doesn't carry it around (?) TODO: wrapping message needs easier. in particular properties and attachments.
@author Kohsuke Kawaguchi
-
com.sun.xml.ws.wsdl.writer.document.Message
@author WS Development Team
-
com.svanloon.game.wizard.network.Message
Document the class
@author svanloon
@version $Rev$, $LastChangedDate$
-
com.taobao.metamorphosis.Message
A message with topic and data,a string attribute is optional.
@author boyan
@Date 2011-4-19
@author wuhua
@Date 2011-6-26
-
com.twilio.sdk.resource.instance.Message
-
com.volantis.mps.bms.Message
Interface representing a Message.
Warning: This is a facade provided for use by user code, not for implementation. User implementations of this interface are highly likely to be incompatible with future releases of the product at both binary and source levels.
@volantis-api-include-in InternalAPI
-
com.volantis.xml.pipeline.sax.impl.drivers.webservice.Message
A Message class contains a collection of parts and provides a means of adding and accessing these parts. The order of parts are significant so they should be added in the correct order since this is the order they will be provided in.
-
com.wordnik.swaggersocket.protocol.Message
A Java object representing the SwaggerSocket protocol implementation.
-
com.zanox.rabbiteasy.Message
A message encapsulates the delivery content of a delivery from a broker. It wraps the body and the message properties and contains commodity methods to access those in an easier fashion.
@author christian.bick
@author uwe.janner
-
com.zeonfederated.mailclient.Message
-
com.zesped.model.Message
-
cu.repsystestbed.simulation.messages.Message
-
cz.matfyz.aai.fantom.message.Message
Base class for all messages going between the client and the server.
-
de.bamberg.ha.api.messaging.Message
-
de.fhkn.in.uce.stun.message.Message
The decoded representation of a message. A message consists of a {@link MessageHeader} and zero or more {@link Attribute}.
@author daniel maier, alexander diener, thomas zink
-
de.hpi.eworld.visualizer.simulation.traci.common.Message
A TraCI message consists of several commands and is used for incoming and outgoing communication.
@author matthias
@see Command
-
de.iritgo.aktera.util.i18n.Message
An adaptation of the ActionMessage class from Struts for use with multiple frameworks. Allows a message key and a number of parameters for replacement to be bundled together. The translation into a "presentation-ready" string is always done by the client (e.g. Struts, Cocoon, etc), not on the server side of Keel.
@author Craig R. McClanahan
@author David Winterfeldt
@author Michael Nash
@version $Revision: 1.1 $ $Date: 2003/12/29 07:01:32 $
-
de.jochenbrissier.backyard.core.Message
an memessage obj. not final TODO: IMRPOVE ...
@author jochen
-
de.mcripper.chatlib.Message
Represents a message in a chat.
@author Niklas Walter
-
de.odysseus.calyxo.base.Message
A message can be considered as a resource which may take arguments. The resource is determined by a bundle and key. Arguments may be added and are of inner class type Arg. The message resource usually resolves to a message template, which is used to merge the arguments into the final message string according to some locale. This message string is produced with the format()
method. Since arguments do not have names, their order is important.
@see de.odysseus.calyxo.base.I18nSupport
@author Christoph Beck
-
de.tfh.pdvl.hp.protocol.Message
@author timo
-
de.tuclausthal.informatik.winf.mobileagents.messaging.Message
A message represents a little message agents can send and receive. A message has a sender and one or more recipients. The body of a message is a String
which may be verified by concrete implementations for validity to the standard of the plattform. This standard will not be defined in this framework, but it's up to the application. Standards could be free-form text, Agent Control Message etc. A specific message type gets registered in the execution environment which clones the given message and uses it for message passing in the system.
A recipient and sender of a message may be an Agent
, a computer or some kind of service in the p2p-network.
@author dluebke
@version 1.0.4 (2003-09-19)
@see java.lang.Cloneable
@since 1.0
-
de.unigoettingen.goobi.module.api.message.Message
-
dijjer.io.comm.Message
A Message which can be read from and written to a DatagramPacket
@author ian
-
domain.Message
@author axe
-
edu.drexel.cs544.mcmuc.actions.Message
A chat room message action must carry a "from" field, which is a nickname that identifies the sender, and a "body" field that carries the user's input. Messages can also optionally contain a "to" value, for which clients can choose to hide from the user messages not meant for them. Messages can also be optionally encrypted with the public key certificate specified by "key". Using "to" and "key" together allows clients to avoid checking the "key" against their own keystore, as they will know the messages was not directed at them. The possible JSON formats are: {'action':'message','from':'','body':''} {'action':'message','from':'','body':'','to',''} {'action':'message','from':'','body':'','key',''} {'action':'message','from':'','body':'','to','','key',''}
-
ee.widespace.forum.Message
Insert the type's description here. Creation date: (2/10/2001 17:11:46 PM)
@author : Jan Abel
-
enterprise.web.tookit.message.Message
@since 25/12/12
@author regis rocha
@description Classe para enviar informacoes para a view, como mensagem de sucesso, erro ou qualquer tipo deinformacao para enviar ao usuario.
-
etc.aloe.data.Message
Stores messages with id, participant, timestamp, and (optionally) labels.
@author Michael Brooks
-
etch.bindings.java.msg.Message
A message is modeled as a command and some argments. The command is an arbitrary integer value, and the arguments are key / value pairs, where the key is an arbitrary integer value and the value is any one of the standard java objects, an ArrayValue, a StructValue, or any type which may be serialized by the ValueFactory.
-
etch.compiler.ast.Message
Description of Message.
-
eu.mosaic_cloud.interoperability.core.Message
-
eu.olol.jrc.util.Message
-
eu.planets_project.ifr.core.wee.api.ReportingLog.Message
-
example.proto.Message
-
facebook4j.Message
-
flex.messaging.messages.Message
Messages are sent from Endpoints into the MessageBroker, which then sends them to a Service. The MessageBroker also sends Messages to Endpoints, and a Service may ask its Broker to send Messages to Endpoints.
@author neville
-
flex2.tools.oem.Message
The
Message
interface lets you discover the following information about a compiler message.
1. getLevel() - Error level: error, warning or info. 2. getPath() - Location. 3. getLine() - Line number. 4. getColumn() - Column number. 5. toString() - Message string.
The
Message.toString()
method returns the message text.
@version 2.0.1
@author Clement Wong
-
fr.cesi.chat.domain.Message
-
fr.tm.elibel.smartqvt.message.Message
A representation of the model object '
Message'.
The following features are supported:
- {@link fr.tm.elibel.smartqvt.message.Message#getStart Start}
- {@link fr.tm.elibel.smartqvt.message.Message#getLength Length}
- {@link fr.tm.elibel.smartqvt.message.Message#getValue Value}
@see fr.tm.elibel.smartqvt.message.MessagePackage#getMessage()
@model abstract="true"
@generated
-
fr.utbm.in56.annonces.model.Message
-
freenet.client.messages.Message
This class represents a message that can be shown in the message panel of the page
-
freenet.io.comm.Message
A Message which can be read from and written to a DatagramPacket. SECURITY REDFLAG WARNING: Messages should normally be recreated rather than passed on. Messages can contain sub-messages, these are used to avoid having to add whole new message types every time we add one field to a message... Passing on a message as-is means it includes the sub-messages, which could lead to e.g. labelling, communication between colluding nodes along a request route, and just wasting bytes. FIXME we should get rid of sub-messages.
@author ian
-
galena.message.Message
-
game.model.dialog.Message
Cette classe est un bean de message, un message comporte un texte et la tete de la personne a qui il est assigné
@author mastersnes
-
global.Message
-
gov.nasa.worldwind.event.Message
-
halfpipe.example.api.Message
-
hamsam.api.Message
le text component } else if(comp instanceof SmileyComponent) { // handle smiley component } else if(comp instanceof URLComponent) { // handle URL component } } }
@author Raghu
-
hello.domain.Message
-
hu.bme.mit.ftsrg.jointstates.command.Message
@author David Lakatos
-
hudson.plugins.growl.util.Message
-
in.partake.model.dto.Message
-
info.aduna.webapp.Message
-
info.walnutstreet.vs.ps02.model.remote.Message
@author Christoph Gostner, Romedius Weiss, Christian Bitschnau
@version 0.1
-
io.fabric8.gateway.handlers.detecting.protocol.openwire.command.Message
Represents an ActiveMQ message
@openwire :marshaller
-
io.iron.ironmq.Message
The Message class represents a message retrieved from an IronMQ queue.
-
ioke.lang.Message
-
iryrwarosh.Message
-
jabber.client.Message
3.org/2001/XMLSchema}anyType"> <sequence> <choice maxOccurs="unbounded" minOccurs="0"> <element ref="{jabber:client}subject"/> <element ref="{jabber:client}body"/> <element ref="{jabber:client}thread"/> </choice> <any/> <element ref="{jabber:client}error" minOccurs="0"/> </sequence> <attribute name="from" type="{http://www.w3.org/2001/XMLSchema}string" /> <attribute name="id" type="{http://www.w3.org/2001/XMLSchema}NMTOKEN" /> <attribute name="to" type="{http://www.w3.org/2001/XMLSchema}string" /> <attribute name="type" default="normal"> <simpleType> <restriction base="{http://www.w3.org/2001/XMLSchema}NCName"> <enumeration value="chat"/> <enumeration value="error"/> <enumeration value="groupchat"/> <enumeration value="headline"/> <enumeration value="normal"/> </restriction> </simpleType> </attribute> <attribute ref="{http://www.w3.org/XML/1998/namespace}lang"/> </restriction> </complexContent> </complexType>
-
javax.jms.Message
@version $Rev: 46019 $ $Date: 2004-09-14 03:56:06 -0600 (Tue, 14 Sep 2004) $
-
javax.mail.Message
@version $Rev: 126350 $ $Date: 2005-01-24 23:35:47 -0700 (Mon, 24 Jan 2005) $
-
javax.management.remote.message.Message
This interface is used to tag an implementing class as a JMXMP protocol message that can be exchanged between the client and the server ends of a JMX API connector.
-
javax.wireless.messaging.Message
This is the base interface for derived interfaces that represent various types of messages. This package is designed to work with
Message
objects that may contain different elements depending on the underlying messaging protocol. This is different from
Datagram
s that are assumed always to be just blocks of binary data. An adapter specification for a given messaging protocol may define further interfaces derived from the
Message
interfaces included in this generic specification.
The wireless messaging protocols that are accessed via this API are typically of store-and-forward nature, unlike network layer datagrams. Thus, the messages will usually reach the recipient, even if the recipient is not connected at the time of sending the message. This may happen significantly later if the recipient is disconnected for a long time. Sending, and possibly also receiving, these wireless messages typically involves a financial cost to the end user that cannot be neglected. Therefore, applications should not send many messages unnecessarily.
This interface contains the functionality common to all messages. Concrete object instances representing a message will typically implement other (sub)interfaces providing access to the content and other information in the message which is dependent on the type of the message.
Object instances implementing this interface are just containers for the data that is passed in. The setAddress()
method just sets the value of the address in the data container without any checking whether the value is valid in any way.
-
javax.wsdl.Message
This interface describes a message used for communication with an operation.
@author Paul Fremantle
@author Nirmal Mukhi
@author Matthew J. Duftler
-
jcurses.util.Message
This is a class to create and show user defined messages. Such message is a dialog with an user defined title, containing an user defined text and a button to close the window with an user defined label.
-
jetbrains.communicator.core.dispatcher.Message
This interface is used both for outgoing messages (network async messages) and for the queue of incoming messages.
A message can deliver itself.
@author Kir
-
jnode.protocol.io.Message
@author kreon
-
juzu.impl.compiler.Message
-
kafka.message.Message
-
kameleon.gui.model.Message
Root class for the messages used in the message system of the model.
@author Schnell Michaël
@version 1.0
-
ket.Message
-
lu.pgd.nssis.ihm.mail.Message
Classe (DTO) pour stocker les informations provenant d'un message de type mail
@author Dominique RIGHETTO (Unilog, a LogicaCMG company) 21 oct. 06
-
lupos.engine.operators.messages.Message
-
marauroa.common.net.message.Message
Message is a class to represent all the kind of messages that are possible to exist in marauroa.
-
message.Message
-
model.Message
-
models.Message
-
mosync.lualiveeditor.MessageQueue.Message
-
msg.Message
-
name.pehl.karaka.client.application.Message
Value object for a message shown in the {@link MessagePresenter}.
@author $Author$
@version $Revision$
-
nanomsg.Message
-
net.alteiar.beans.chat.Message
-
net.cloudcodex.server.data.Data.Message
-
net.ex337.scriptus.model.api.Message
-
net.gleamynode.netty2.Message
-
net.java.sip.communicator.service.protocol.Message
Used to access the content of instant messages that are sent or received via the instant messaging operation set.
This class provides easy access to the content and key fields of an instant Message. Content types are represented using MIME types. [IETF RFC 2045-2048].
Messages are created through the OperationSetBaicInstanceMessaging operation set.
All messages have message ids that allow the underlying implementation to notify the user of their successful delivery.
@author Emil Ivov
-
net.jxta.endpoint.Message
-
net.kindleit.gae.example.model.Message
-
net.lightstone.msg.Message
-
net.paoloambrosio.model.Message
-
net.reversehttp.messaging.Message
-
net.rim.blackberry.api.mail.Message
-
net.rim.device.api.io.messaging.Message
-
net.schmizz.sshj.common.Message
-
net.sf.gilead.sample.domain.Message
Message Java 1.4 domain class for stateless pojo store This class just has to inherit from LightEntity; The 'Keywords' property has private getter and setter
@author bruno.marchesson
-
net.sf.pmr.messageBoards.domain.Message
@author ArnaudTODO To change the template for this generated type comment go to Window - Preferences - Java - Code Style - Code Templates
-
net.sf.saxon.instruct.Message
An xsl:message element in the stylesheet.
-
net.sf.xbus.protocol.Message
Message
is the base for all classes that handle the data of requests and responses. It contains all methods and attributes which are independent of the application-protocol.
-
net.solosky.maplefetion.bean.Message
聊天消息 聊天的内容是很丰富的,有字体,颜色,大小,图片等。。 这里暂时只对字体,颜色,大小做支持,其他的逐步添加
@author solosky
-
net.tomp2p.message.Message
The message is in binary format in TomP2P. It has several header and payload fields. Since we do the serialization/encoding manually, we do not need a serialization field.
@author Thomas Bocek
-
net.windwards.dnsfrontend.dialog.Message
Created by quest on 2014-05-05.
-
net.yura.lobby.model.Message
@author Yura Mamyrin
-
network.Message
-
nexj.core.meta.integration.Message
Message metadata.
-
ninja.utils.Message
A pojo to be renderd as Json or Xml. Used for instance to display error messages when a route is not found.
-
nu.fw.jeti.jabber.elements.Message
Title: im
Description:
Copyright: Copyright (c) 2001
Company:
@author E.S. de Boer
@version 1.0
-
org.activiti.bpmn.model.Message
@author Tijs Rademakers
-
org.activiti.rest.api.jpa.model.Message
-
org.antlr.tool.Message
The ANTLR code calls methods on ErrorManager to report errors etc... Rather than simply pass these arguments to the ANTLRErrorListener directly, create an object that encapsulates everything. In this way, the error listener interface does not have to change when I add a new kind of error message. I don't want to break a GUI for example every time I update the error system in ANTLR itself. To get a printable error/warning message, call toString().
-
org.apache.activemq.apollo.openwire.command.Message
Represents an ActiveMQ message
@openwire :marshaller
-
org.apache.activemq.command.Message
Represents an ActiveMQ message
@openwire :marshaller
@version $Revision$
-
org.apache.avro.Protocol.Message
-
org.apache.avro.test.Message
-
org.apache.axis.Message
@author Doug Davis (dug@us.ibm.com)
@author Glen Daniels (gdaniels@allaire.com)
-
org.apache.axis2.jaxws.message.Message
Message
A Message represents the XML + Attachments
Most of the methods available on a message are only applicable to the XML part of the Message. See the XMLPart interface for an explantation of these methods.
@see XMLPart
@see Attachment
-
org.apache.camel.Message
emq.apache.org/camel/message.html">Message pattern and represents an inbound or outbound message as part of an {@link Exchange}
@version $Revision: 564677 $
-
org.apache.camel.dataformat.bindy.annotation.Message
-
org.apache.cassandra.net.Message
-
org.apache.cometd.bayeux.Message
A Bayeux Message
A Bayeux message is a Map of String/Object key value pairs representing the data in the message. The message contains information about the channel it was published through and who the sender was
@author Greg Wilkins
@author Filip Hanik
-
org.apache.commons.scaffold.util.Message
-
org.apache.cxf.common.i18n.Message
-
org.apache.cxf.message.Message
The base interface for all all message implementations. All message objects passed to interceptors use this interface.
-
org.apache.deltaspike.core.api.message.Message
Basic interface for all messages.
A Message
is not a simple String but all the information needed to create those Strings for multiple situations. The situation ist determined by the used {@link MessageContext}.
-
org.apache.directory.api.ldap.model.message.Message
-
org.apache.directory.shared.ldap.model.message.Message
-
org.apache.etch.bindings.java.msg.Message
A message is modeled as a command and some argments. The command is an arbitrary integer value, and the arguments are key / value pairs, where the key is an arbitrary integer value and the value is any one of the standard java objects, an ArrayValue, a StructValue, or any type which may be serialized by the ValueFactory.
-
org.apache.etch.compiler.ast.Message
Description of Message.
-
org.apache.hedwig.protocol.PubSubProtocol.Message
-
org.apache.helix.model.Message
-
org.apache.james.jdkim.impl.Message
The header of an entity (see RFC 2045).
-
org.apache.james.mailbox.store.mail.model.Message
A MIME message, consisting of meta-data (including MIME headers) plus body content. In the case of multipart documents, this body content has internal structure described by the meta-data.
-
org.apache.james.mime4j.dom.Message
An MIME message (as defined in RFC 2045).
-
org.apache.james.mime4j.message.Message
Represents a MIME message. The following code parses a stream into a
Message
object.
Message msg = new Message(new FileInputStream("mime.msg"));
@version $Id: Message.java,v 1.3 2004/10/02 12:41:11 ntherning Exp $
-
org.apache.lenya.notification.Message
A notification message.
-
org.apache.logging.log4j.message.Message
An interface for various Message implementations that can be logged. Messages can act as wrappers around Objects so that user can have control over converting Objects to Strings when necessary without requiring complicated formatters and as a way to manipulate the message based on information available at runtime such as the locale of the system.
Note: Message objects should not be considered to be thread safe nor should they be assumed to be safely reusable even on the same thread. The logging system may provide information to the Message objects and the Messages might be queued for asynchronous delivery. Thus, any modifications to a Message object by an application should by avoided after the Message has been passed as a parameter on a Logger method.
@doubt Interfaces should rarely extend Serializable according to Effective Java 2nd Ed pg 291.(RG) That section also says "If a class or interface exists primarily to participate in a framework that requires all participants to implement Serializable, then it makes perfect sense for the class or interface to implement or extend Serializable". Such is the case here as the LogEvent must be Serializable.
-
org.apache.lucene.messages.Message
Message Interface for a lazy loading. For Native Language Support (NLS), system of software internationalization.
-
org.apache.lucene.queryparser.flexible.messages.Message
Message Interface for a lazy loading. For Native Language Support (NLS), system of software internationalization.
-
org.apache.myfaces.extensions.cdi.message.api.Message
@author Manfred Geiler
@author Gerhard Petracek
-
org.apache.myfaces.wap.component.Message
-
org.apache.ode.bpel.iapi.Message
A representation of a WSDL-typed message. The implementation of this interface is provided by the integration layer. TODO: flush this out WRT Sybase requirements. TODO: should we provide meta-data through this interface or will that put an undue burden on the integration layer?
-
org.apache.olingo.odata2.core.exception.MessageService.Message
-
org.apache.openjpa.lib.util.Localizer.Message
-
org.apache.openjpa.persistence.callbacks.Message
A very simple persistent entity that holds a "message", has a "created" field that is initialized to the time at which the object was created, and an id field that is initialized to the current time.
-
org.apache.pig.penny.impl.comm.Message
-
org.apache.qpid.amqp_1_0.client.Message
-
org.apache.qpid.api.Message
-
org.apache.qpid.proton.message.Message
-
org.apache.qpidity.api.Message
-
org.apache.s4.client.Message
Messages that can be send/received by client. They typically correspond to events that are sent/received.
-
org.apache.servicemix.jbi.api.Message
-
org.apache.servicemix.nmr.api.Message
The Message represents the content of a request, a response or a fault. Messages are part of {@link Exchange}s are created using {@link Exchange#getIn()}, {@link Exchange#getOut()} and {@link Exchange#getFault()}. If the Exchange has to go to a remote ServiceMix instance to be processed (if the instance is part of a cluster), all headers, attachments and content have to be Serializable. TODO: security
@version $Revision: $
@since 4.0
-
org.apache.servicemix.soap.api.Message
-
org.apache.shindig.social.opensocial.model.Message
-
org.apache.sling.i18n.impl.Message
Helper class for creating test data in a generic way.
-
org.apache.soap.messaging.Message
A Message
is the class whose instances represent one-way messages in SOAP. While messages are one-way, they are sometimes carried on two-way transports such as HTTP. To accomodate that, the API supported here has a "receive" method as well - that is only applicable if the transport that is being used supports the receive() method (@see org.apache.soap.transport.SOAPTransport) so that this API can get at the 'response' envelope.
@author Sanjiva Weerawarana (sanjiva@watson.ibm.com)
-
org.apache.tools.ant.taskdefs.email.Message
Class representing an email message.
@since Ant 1.5
-
org.apache.tuscany.core.message.Message
Represents a request, response, or exception flowing through a wire
@version $Rev $Date
-
org.apache.tuscany.sca.invocation.Message
Represents a request, response, or exception flowing through a wire
@version $Rev $Date
-
org.apache.tuscany.spi.wire.Message
Represents a request, response, or exception flowing through a wire
@version $Rev $Date
-
org.apache.twill.internal.state.Message
-
org.apache.zookeeper.server.quorum.QuorumCnxManager.Message
-
org.ardverk.dht.message.Message
The base interface for messages.
-
org.aspectj.bridge.Message
Implement messages. This implementation is immutable if ISourceLocation is immutable.
-
org.astrogrid.samp.Message
-
org.auraframework.system.Message
-
org.axonframework.domain.Message
Representation of a Message, containing a Payload and MetaData. Typical examples of Messages are Commands and Events.
Instead of implementing
Message
directly, consider implementing {@link org.axonframework.commandhandling.CommandMessage
CommandMessage
} or {@link EventMessage} instead.
@param < T> The type of payload contained in this Message
@author Allard Buijze
@see org.axonframework.commandhandling.CommandMessage
CommandMessage
@see EventMessage
@since 2.0
-
org.b3log.latke.mail.MailService.Message
-
org.beangle.notification.Message
-
org.butor.utils.Message
TODO
@author sawanaiJul 1, 2004
-
org.carrot2.labs.smartsprites.message.Message
Represents a processing message, can be an information message or a warning.
-
org.chromium.debug.ui.DialogUtils.Message
-
org.chromium.sdk.internal.transport.Message
A transport message encapsulating the data sent/received over the wire (protocol headers and content). This class can serialize and deserialize itself into a BufferedWriter according to the ChromeDevTools Protocol specification. Content-Length field is a transparent field: it gets added and processed on read/write phase. It is not reported to user.
-
org.codehaus.groovy.control.messages.Message
A base class for compilation messages.
@author
Chris Poirier
@version $Id: Message.java 14269 2008-12-04 16:06:13Z blackdrag $
-
org.codemap.communication.messages.Message
TODO check if we should implement IModelChangeMessage, like
@see org.eclipse.ecf.docshare.messages.Message
@author deif
-
org.cometd.Message
-
org.cometd.bayeux.Message
The Bayeux protocol exchange information by means of messages.
This interface represents the API of a Bayeux message, and consists mainly of convenience methods to access the known fields of the message map.
This interface comes in both an immutable and {@link Mutable mutable} versions.Mutability may be deeply enforced by an implementation, so that it is not correct to cast a passed Message, to a Message.Mutable, even if the implementation allows this.
-
org.dago.wecommand.wiimote.messages.Message
BT Message interface.
-
org.darkhelm.dragonchess.shared.channel.Message
Used for serializing and deserializing objects. You need to implement this to send objects
@author Eirik Brandtzæg
-
org.drools.Message
-
org.drools.bpmn2.core.Message
-
org.drools.compiler.Message
-
org.drools.example.api.namedkiesession.Message
-
org.drools.example.cdi.cdiexample.Message
-
org.drools.grid.generic.Message
-
org.drools.grid.io.Message
-
org.drools.integrationtests.helloworld.Message
-
org.dspace.app.xmlui.wing.Message
This class represents an i18n message, which is composed of three parts: a catalogue, a key, and a set of dictionary parameters. The catalogue tells the translater where to find the key, the key tells the transformer which specific text should be used, and the parameters provide for non translated data to be inserted into the resulting string. This class design such that the Message object can be made static my any class that needs to use it. If dicionary parameters are used then a new instance is created specificaly for those parameters, this prevents concurent threads from over writting parameters of each other.
@author Scott Phillips
-
org.eclipse.bpmn2.Message
A representation of the model object '
Message'.
The following features are supported:
- {@link org.eclipse.bpmn2.Message#getItemRef Item Ref}
- {@link org.eclipse.bpmn2.Message#getName Name}
@see org.eclipse.bpmn2.Bpmn2Package#getMessage()
@model extendedMetaData="name='tMessage' kind='elementOnly'"
@generated
-
org.eclipse.jdt.core.dom.Message
Error message used to report potential errors found during the AST parsing or name resolution. Instances of this class are immutable.
@since 2.0
-
org.eclipse.wst.validation.internal.core.Message
-
org.eclipse.wst.wsdl.Message
A representation of the model object '
Message'.
@since 1.0
@ignore This class represents a WSDL message element. A WSDL message is an abstract, typed definition of the data being communicated.
The following features are supported:
- {@link org.eclipse.wst.wsdl.Message#getQName QName}
- {@link org.eclipse.wst.wsdl.Message#isUndefined Undefined}
- {@link org.eclipse.wst.wsdl.Message#getEParts EParts}
@see org.eclipse.wst.wsdl.WSDLPackage#getMessage()
@model superTypes="org.eclipse.wst.wsdl.ExtensibleElement org.eclipse.wst.wsdl.IMessage"
@generated
-
org.ejbca.extra.db.Message
Message is a JPA entity for storing requests and responses for the External RA
@version $Id: Message.java 9330 2010-06-30 18:16:53Z anatom $
-
org.elasticsearch.common.inject.spi.Message
An error message and the context in which it occured. Messages are usually created internally by Guice and its extensions. Messages can be created explicitly in a module using {@link org.elasticsearch.common.inject.Binder#addError(Throwable) addError()} statements:
try { bindPropertiesFromFile(); } catch (IOException e) { addError(e); }
@author crazybob@google.com (Bob Lee)
-
org.ethereum.net.message.Message
Abstract message class for all messages on the Ethereum network
@author Roman MandeleilCreated on: 06/04/14 14:58
-
org.exoplatform.services.mail.Message
Created by The eXo Platform SAS Author : Phung Hai Nam phunghainam@gmail.com Dec 28, 2005
-
org.exoplatform.services.remote.group.Message
@author Tuan Nguyen (tuan08@users.sourceforge.net)
@since Feb 21, 2005
@version $Id: Message.java 5799 2006-05-28 17:55:42Z geaz $
-
org.fedorahosted.tennera.jgettext.Message
-
org.fenixedu.academic.domain.util.email.Message
-
org.focusns.model.msg.Message
-
org.freerealm.player.Message
@author Deniz ARIKAN
-
org.fto.jthink.sample.mboard.po.Message
-
org.fusesource.ide.jmx.commons.messages.Message
-
org.fusesource.mqtt.client.Message
irino.com">Hiram Chirino
-
org.glassfish.jersey.examples.jersey_ejb.entities.Message
Message bean representing a single message.
@author Pavel Bucek (pavel.bucek at oracle.com)
-
org.graylog2.plugin.Message
-
org.gudy.azureus2.plugins.messaging.Message
Basic peer message. A message is uniquely identified by the combination of ID and version.
-
org.gwtnode.dev.debug.message.Message
@author Chad Retz
-
org.hibernate.search.indexes.serialization.operations.impl.Message
A message is made of: - a protocol version number - a set of operations
@author Emmanuel Bernard
-
org.hornetq.api.core.Message
A Message is a routable instance that has a payload.
The payload (the "body") is opaque to the messaging system. A Message also has a fixed set of headers (required by the messaging system) and properties (defined by the users) that can be used by the messaging system to route the message (e.g. to ensure it matches a queue filter).
Message Properties
Message can contain properties specified by the users. It is possible to convert from some types to other types as specified by the following table:
| | boolean byte short int long float double String byte[] |---------------------------------------------------------------- |boolean | X X |byte | X X X X X |short | X X X X |int | X X X |long | X X |float | X X X |double | X X |String | X X X X X X X X |byte[] | X |-----------------------------------------------------------------
If conversion is not allowed (for example calling {@code getFloatProperty} on a property set a{@code boolean}), a {@link PropertyConversionException} will be thrown.
@author
Tim Fox
@author
ClebertSuconic
@version
$Revision: 3341 $ $Id: Message.java 3341 2007-11-19 14:34:57Z timfox $
-
org.infoglue.cms.entities.management.Message
-
org.internna.ossmoney.model.qif.Message
-
org.jacorb.notification.interfaces.Message
@author Alphonse Bendt
@version $Id: Message.java,v 1.9 2006-02-25 15:28:40 alphonse.bendt Exp $
-
org.japura.message.Message
Copyright (C) 2011-2013 Carlos Eduardo Leite de Andrade
This library is free software: you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public License along with this program. If not, see www.gnu.org/licenses/
For more information, contact: www.japura.org
@author Carlos Eduardo Leite de Andrade
-
org.jasig.portal.i18n.Message
This interface represents localized messages used in database message source in order to enable internationalization of dynamic messages like group names, tab titles, etc.
@author Arvids Grabovskis
@version $Revision$
-
org.javagroups.Message
-
org.jboss.aerogear.unifiedpush.message.Message
ear.org/docs/specs/aerogear-push-messages/">Message Format Specification.
-
org.jboss.as.console.client.core.message.Message
A message to be displayed to the user in one or more places.
@author Greg Hinkle
@author Ian Springer
-
org.jboss.blacktie.jatmibroker.core.transport.Message
-
org.jboss.dashboard.commons.message.Message
A message.
-
org.jboss.errai.bus.client.Message
A simple interface for defining a message.
-
org.jboss.errai.bus.client.api.Message
-
org.jboss.errai.bus.client.api.messaging.Message
Contract for all messages that can be transmitted on the {@link MessageBus}.
Message instances are normally created with the help of {@link MessageBuilder}, but individual Message implementations may also be created directly if desired.
@author Mike Brock
@author Jonathan Fuerth
@author Christian Sadilek
-
org.jboss.messaging.core.contract.Message
A message is a routable instance that has a payload. The payload is opaque to the messaging system.
@author
Ovidiu Feodorov
@author
Tim Fox
@version
$Revision: 3337 $$Id: Message.java 3337 2007-11-16 12:22:58Z timfox $
-
org.jboss.messaging.core.message.Message
A message is a routable instance that has a payload. The payload is opaque to the messaging system. When implementing this interface, make sure you override equals() and hashCode() such that two Message instances with equals IDs are equal.
@author
Ovidiu Feodorov
@author
Tim Fox
@version
$Revision: 2202 $$Id: Message.java 2202 2007-02-08 10:50:26Z timfox $
-
org.jboss.narayana.blacktie.jatmibroker.core.transport.Message
-
org.jboss.seam.solder.messages.Message
-
org.jboss.test.ws.jaxrpc.jbws1427.services.Message
-
org.jbpm.Message
-
org.jbpm.bpmn2.core.Message
-
org.jbpm.env.session.Message
@author Tom Baeyens
-
org.jbpm.msg.Message
-
org.jclouds.openstack.marconi.v1.domain.Message
A message to be sent to a queue.
-
org.jclouds.sqs.domain.Message
zonwebservices.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/MessageLifecycle.html"
>doc
@author Adrian Cole
-
org.jdesktop.jdic.desktop.Message
-
org.jdesktop.wonderland.common.messages.Message
The base type of a message in the Wonderland system.
Every message in the system has a unique identifier. This identifier is unique within the context of the session that created it, but may not be globally unique. For message that need to be unique across clients, the session id of the originating session should be included in the message.
Wonderland messages are by default serialized and sent to clients. Messages that are very frequent should be hand-packed using the Externalizable interface.
@see java.io.Externalizable
@author jkaplan
-
org.jgroups.Message
A Message encapsulates data sent to members of a group. It contains among other things the address of the sender, the destination address, a payload (byte buffer) and a list of headers. Headers are added by protocols on the sender side and removed by protocols on the receiver's side.
The byte buffer can point to a reference, and we can subset it using index and length. However, when the message is serialized, we only write the bytes between index and length.
@author Bela Ban
@version $Id: Message.java,v 1.94 2008/11/11 09:30:08 belaban Exp $
-
org.jibx.ws.wsdl.model.Message
WSDL object model components corresponding to a message definition.
@author Dennis M. Sosnoski
-
org.jivesoftware.smack.packet.Message
Represents XMPP message packets. A message can be one of several types:
- Message.Type.NORMAL -- (Default) a normal text message used in email like interface.
- Message.Type.CHAT -- a typically short text message used in line-by-line chat interfaces.
- Message.Type.GROUP_CHAT -- a chat message sent to a groupchat server for group chats.
- Message.Type.HEADLINE -- a text message to be displayed in scrolling marquee displays.
- Message.Type.ERROR -- indicates a messaging error.
For each message type, different message fields are typically used as follows:
| Message type |
Field | Normal | Chat | Group Chat | Headline | XMPPError |
subject | SHOULD | SHOULD NOT | SHOULD NOT | SHOULD NOT | SHOULD NOT |
thread | OPTIONAL | SHOULD | OPTIONAL | OPTIONAL | SHOULD NOT |
body | SHOULD | SHOULD | SHOULD | SHOULD | SHOULD NOT |
error | MUST NOT | MUST NOT | MUST NOT | MUST NOT | MUST |
@author Matt Tucker
-
org.joget.apps.app.model.Message
-
org.jpokemon.server.Message
-
org.jresearch.gossip.beans.forum.Message
DOCUMENT ME!
@author Bel
-
org.kie.api.builder.Message
-
org.mime4j.message.Message
-
org.mokai.Message
Represents a message that is being routing through the gateway.
@author German Escobar
-
org.moltools.apps.probemaker.messages.Message
Description: A class that represents a message appended to a MessageHolder. A message specifies a message type, a severity, and contains a message string
@author Johan Stenberg
@version 1.0
-
org.msgpack.annotation.Message
-
org.mule.config.i18n.Message
-
org.mule.module.pgp.Message
-
org.nasutekds.messages.Message
Renders sensitive textural strings. In most cases message are intended to render textural strings in a locale-sensitive manner although this class defines convenience methods for creating uninternationalized Message
objects that render the same text regardless of the requested locale. This class implements CharSequence
so that messages can be supplied as arguments to other messages. This way messages can be composed of fragments of other messages if necessary.
@see org.nasutekds.messages.MessageDescriptor
-
org.nemesis.forum.Message
A ForumMessage encapsulates message data. Each message belongs to a thread, and relates to other messages in a thread in a tree relationship. This system allows messages to represent threaded conversations. For example:
[thread] |- [message] |- [message] |- [message] |- [message] |- [message] |- [message]
Each message has a subject and body. Messages are authored by a user in the system or can be anonymous. An ID is given to each message so that it can be tracked uniquely. Because is possible that one might want to store considerable more information with each message besides a subject and body, each message can have an arbitrary number of properties. For example, a property "IP" could be stored with each message that records the IP address of the person posting the message for security reasons.
The creation date, and the date the message was last modified are maintained for each message.
For added functionality, any number of filters can be applied to a message. Filters dynamically format the subject and body of a message. Methods are also provided to bypass filters.
@see ForumMessageFilter
-
org.objectweb.celtix.common.i18n.Message
-
org.objectweb.joram.client.jms.Message
Implements the
javax.jms.Message
interface.
A Joram message encapsulates a proprietary message which is also used for effective MOM transport facility.
-
org.objectweb.joram.mom.messages.Message
The
Message
class actually provides the transport facility for the data exchanged during MOM operations.
A message content is always wrapped as a bytes array, it is characterized by properties and "header" fields.
-
org.objectweb.joram.shared.messages.Message
Implements the Message
data structure.
-
org.olat.modules.fo.Message
@author schneider
-
org.opends.messages.Message
-
org.openhab.binding.maxcube.internal.message.Message
Base message received by the MAX!Cube protocol.
@author Andreas Heil (info@aheil.de)
@since 1.4.0
-
org.openid4java.message.Message
@author Marius Scurtescu, Johnny Bufu
-
org.osforce.connect.entity.message.Message
ourceforce.org">开源力量
-
org.owasp.webscarab.model.Message
Message is a class that is used to represent the bulk of an HTTP message, namely the headers, and (possibly null) body. Messages should not be instantiated directly, but should rather be created by a derived class, namely Request or Response.
@author rdawes
-
org.pdf4j.saxon.instruct.Message
An xsl:message element in the stylesheet.
-
org.phoenixdb.io.network.Message
Base class for constructing network messages locally and from socket stream
-
org.planx.routing.messaging.Message
-
org.quna.rsc.data.message.Message
-
org.rhq.coregui.client.util.message.Message
A message to be displayed to the user in one or more places.
@author Greg Hinkle
@author Ian Springer
-
org.richfaces.javascript.Message
@author asmirnov
-
org.rzo.yajsw.controller.Message
The Class Message.
-
org.sbml.jsbml.util.Message
@since 0.8
@version $Rev: 1524 $
-
org.smslib.Message
The parent of all message-related classes. Most of common fields and attributes of both inbound and outbound messages are placed in this class.
-
org.sonar.server.exceptions.Message
-
org.spout.api.protocol.Message
-
org.springbyexample.schema.beans.response.Message
-
org.springframework.amqp.core.Message
The 0-8 and 0-9-1 AMQP specifications do not define an Message class or interface. Instead, when performing an operation such as basicPublish the content is passed as a byte-array argument and additional properties are passed in as separate arguments. Spring AMQP defines a Message class as part of a more general AMQP domain model representation. The purpose of the Message class is to simply encapsulate the body and properties within a single instance so that the rest of the AMQP API can in turn be simpler.
@author Mark Pollack
@author Mark Fisher
@author Oleg Zhurakousky
@author Dave Syer
@author Gary Russell
-
org.springframework.binding.message.Message
An object of communication that provides text information. For example, a validation message may inform a web application user a business rule was violated. A message can be associated with a particular source element or component, has text providing the basis for communication, and has severity indicating the priority or intensity of the message for its receiver.
@author Keith Donald
-
org.springframework.data.redis.connection.Message
Class encapsulating a Redis message body and its properties.
@author Costin Leau
-
org.springframework.integration.Message
-
org.springframework.integration.core.Message
-
org.springframework.integration.message.Message
-
org.springframework.messaging.Message
A generic message representation with headers and body.
@author Mark Fisher
@author Arjen Poutsma
@since 4.0
@see org.springframework.messaging.support.MessageBuilder
-
org.springframework.richclient.core.Message
An interface to be implemented by classes that represent a user-oriented message and are capable of rendering themselves on GUI components.
@see JComponent
-
org.springframework.samples.mvc.flash.FlashMap.Message
-
org.springframework.security.samples.data.Message
-
org.springframework.social.popup.message.Message
A message to display to the user. Has a type indicating the kind of message.
@author Keith Donald
-
org.springframework.social.showcase.message.Message
A message to display to the user. Has a type indicating the kind of message.
@author Keith Donald
-
org.springmodules.xt.model.notification.Message
Interface representing a message to be notified.
Each message has a code, a default message string, a property name, and a type.
This interface has only getter methods because a message should be immutable.
@author Sergio Bossa
-
org.structr.cloud.message.Message
@author Christian Morgner
-
org.switchyard.Message
A {@code Message} represents an individual input or output of a service, thecontent of which is interpreted by service implementation logic. A Message does not carry context specific to a service invocation, which means that it can be copied and reused across service invocations.
There are two distinct parts to a message:
- Content : the main body, or payload, of the message. There is only one body per message instance. The message body is mutable, so message processing logic can access the content, change it (transform, enrich, etc.), and then set it back on the message.
- Attachments : provide the ability to associate content with a message separate from the main body, allowing it to be parsed independently. One example would be a binary image that is referenced by the main body of the message. The attachment may be too large to be processed in certain services or the service implementation may not be able to parse/interpret it.
-
org.teiid.net.socket.Message
-
org.terasology.logic.console.Message
@author Immortius
-
org.umundo.core.Message
-
org.uned.agonzalo16.bitacora.domain.Message
-
org.vertx.java.core.eventbus.Message
g">Tim Fox
-
org.voltcore.agreement.FakeMesh.Message
-
org.vosao.business.mq.Message
@author Alexander Oleynik
-
org.vraptor.i18n.Message
-
org.waveprotocol.pst.model.Message
Wraps a {@link Descriptor} with methods suitable for stringtemplate.
@author kalman@google.com (Benjamin Kalman)
-
org.wicketstuff.iolite.persistence.domain.Message
-
org.wijiscommons.ssaf.message.Message
-
org.wso2.carbon.event.core.Message
this class is used to keep the OMMessage and
-
org.wso2.carbon.registry.social.api.message.Message
This interface models the Messages
-
org.wso2.carbon.registry.synchronization.message.Message
A representation of a message presented to a user during the process of synchronizing a given registry instance with a specified location on the filesystem.
-
org.wso2.carbon.rulecep.adapters.Message
Message as a Fact. Provides a way to insert message as a fact into the rule engine. This is a type of TransientObject
-
org.xbill.DNS.Message
A DNS Message. A message is the basic unit of communication between the client and server of a DNS operation. A message consists of a Header and 4 message sections.
@see Resolver
@see Header
@see Section
@author Brian Wellington
-
org.xmatthew.spy2servers.core.Message
@author Matthew Xie
-
org.xmpp.packet.Message
Message packet.
A message can have one of several {@link Type Types}. For each message type, different message fields are typically used as follows:
| Message type |
Field | Normal | Chat | Group Chat | Headline | Error |
subject | SHOULD | SHOULD NOT | SHOULD NOT | SHOULD NOT | SHOULD NOT |
thread | OPTIONAL | SHOULD | OPTIONAL | OPTIONAL | SHOULD NOT |
body | SHOULD | SHOULD | SHOULD | SHOULD | SHOULD NOT |
error | MUST NOT | MUST NOT | MUST NOT | MUST NOT | MUST |
-
org.xrace.model.Message
-
org.zaproxy.zap.extension.httppanel.Message
-
org.zeroexchange.model.message.Message
The message allows users communicate with each other and be informed concerning system's events.
@author black
-
org.zoolu.sip.message.Message
Class Message extends class sip.message.BaseMessage adding some SIP extensions.
Class Message supports all methods and header definened in RFC3261, plus:
- method MESSAGE (RFC3428) >
- method REFER (RFC3515) >
- header Refer-To >
- header Referred-By >
- header Event >
-
parrot.server.data.objects.Message
-
plugins.Freetalk.Message
A Freetalk message. This class is supposed to be used by the UI directly for reading messages. The UI can obtain message objects by querying them from a MessageManager
. A message has the usual attributes (author, boards to which it is posted, etc.) one would assume. There are two unique ways to reference a message: It's URI and it's message ID. The URI is to be given to the user if he wants to tell other people about the message, the message ID is to be used for querying the database for a message in a fast way. Activation policy: Class Message does automatic activation on its own. This means that objects of class Message can be activated to a depth of only 1 when querying them from the database. All methods automatically activate the object to any needed higher depth.
@author xor (xor@freenetproject.org)
@author saces
-
pong.common.Message
A message that will be sent via network for client/server communication.
@author Lorenzo Gatto
-
powermock.examples.spring.Message
-
programming5.net.Message
This class is used to store and manipulate an organized array of items in a message context of header and body items, to produce encoded messages of the following syntax: [header]:[item{::item}]
There are no restrictions on the syntax of the items. If constructing a message string by hand, however, take care that all sequences of consecutive colons (::) correspond to message separators; otherwise, the message will be decoded incorrectly. Additionally, if colon-slash sequences (:/) exist in an item, they will be modified by the decoding methods. In both these cases, adding a slash after the first colon will allow correct decoding of the message items; this is precisely what is done when messages are encoded normally, to allow for arbitrary syntax of message items.
Note that the shortest valid message is a single colon (:) (message with no header and no body) and that all messages must have at least one colon.
As of version 6.1, the internal encoding of messages is handled with arrays of bytes, to prevent conversion errors when encoding byte arrays as strings. For the basic types, these arrays correspond to the byte representation of the items' string representations, not their internal numeric representation. Byte array accessors were added to manipulate these items directly as byte arrays, for serialized objects or raw byte payloads.
@author Andres Quiroz Hernandez
@version 6.19
-
quickfix.Message
-
realityshard.container.network.Message
-
rinde.sim.core.model.communication.Message
@author Bartosz Michalik
-
rocks.xmpp.core.stanza.model.client.Message
The implementation of the {@code } element for the client namespace ('jabber:client').
@author Christian Schudt
-
scap.check.Message
-
scotlandyard.shared.messaging.Message
@author Felipe Blassioli Base class for all types of messages. It has agetPayload method that must be overrided by all subclasses.
-
seph.lang.ast.Message
-
server.common.Message
@author Bernard , Romain
-
server.protocol.Message
The Class Message. Holds the content for a string message that will be broadcasted.
@author Priit Laht
-
shared.Message
-
simpleserver.message.Message
-
soc.qase.com.message.Message
The message class implements all general functionality of messages sent between client/host and host/client.
-
system.Message
Represents messages that are communicated among Vertices at the end of a superstep.
@author Manasa Chandrasekhar
@author Kowshik Prakasam
-
test.common.Message
-
trams.data.Message
Class representing a message in TraMS.
@author Dave Lee
-
ucar.nc2.iosp.bufr.Message
-
uk.ac.cam.cl.fjava.messages.Message
-
uk.org.microbase.notification.db.data.Message
Stores a single message in the notification system database. A message has a number of fields that serve the different needs of different types of consumers. The primary purpose of a message is to store application-specific content for communication among responders. This data is stored in
content
and
binaryContent
, respectively. Messages store a number of other fields for a variety of purposes, including:
- Data of use to Microbase housekeeping processes - current processing states of various responders (e.g., PROCESSING, SUCCESS, ERROR states.
- Provenance data, such as which responder published the data, when it was published, what user data set the message is associated with, etc.
Once published, message content is immutable except for the following:
- Responder state flags that are updated according to the outcome of message processing by various responders
- metaTags - user writable tags that may be added, modified or deleted at any time.
@author Keith Flanagan
-
us.aaronweiss.juicebot.Message
An immutable received message over IRC.
@author Aaron Weiss
@version 1.0.1
@since 2.0.0
-
winterwell.jtwitter.Twitter.Message