-
com.caucho.jms.message.MessageImpl
A basic message.
-
com.ibm.wsdl.MessageImpl
This class describes a message used for communication with an operation.
@author Paul Fremantle
@author Nirmal Mukhi
@author Matthew J. Duftler
-
com.sun.xml.internal.messaging.saaj.soap.MessageImpl
The message implementation for SOAP messages with attachments. Messages for specific profiles will likely extend this MessageImpl class and add more value for that particular profile.
@author Anil Vijendran (akv@eng.sun.com)
@author Rajiv Mordani (rajiv.mordani@sun.com)
@author Manveen Kaur (manveen.kaur@sun.com)
-
com.sun.xml.messaging.saaj.soap.MessageImpl
The message implementation for SOAP messages with attachments. Messages for specific profiles will likely extend this MessageImpl class and add more value for that particular profile.
@author Anil Vijendran (akv@eng.sun.com)
@author Rajiv Mordani (rajiv.mordani@sun.com)
@author Manveen Kaur (manveen.kaur@sun.com)
-
hermes.providers.messages.MessageImpl
@author colincrist@hermesjms.com
@version $Id: MessageImpl.java,v 1.6 2005/06/28 15:36:01 colincrist Exp $
-
net.sf.pmr.messageBoards.domain.MessageImpl
@author ArnaudTODO To change the template for this generated type comment go to Window - Preferences - Java - Code Style - Code Templates
-
org.apache.commons.scaffold.util.MessageImpl
-
org.apache.cxf.message.MessageImpl
-
org.apache.ivy.util.MessageImpl
-
org.apache.james.mime4j.message.MessageImpl
Default implementation of {@link Message}.
-
org.apache.lucene.messages.MessageImpl
Default implementation of Message interface. For Native Language Support (NLS), system of software internationalization.
-
org.apache.lucene.queryparser.flexible.messages.MessageImpl
Default implementation of Message interface. For Native Language Support (NLS), system of software internationalization.
-
org.apache.ode.bpel.engine.MessageImpl
-
org.apache.qpid.proton.message.impl.MessageImpl
-
org.apache.servicemix.nmr.core.MessageImpl
The default {@link Message} implementation.
@version $Revision: $
@since 4.0
-
org.apache.servicemix.soap.core.MessageImpl
-
org.apache.shindig.social.core.model.MessageImpl
-
org.apache.tomcat.bayeux.MessageImpl
-
org.apache.tuscany.sca.core.invocation.MessageImpl
The default implementation of a message flowed through a wire during an invocation
@version $Rev $Date
-
org.apache.tuscany.sca.core.invocation.impl.MessageImpl
The default implementation of a message flowed through a wire during an invocation
@version $Rev $Date: 2008-12-03 22:05:21 -0800 (Wed, 03 Dec 2008) $
-
org.apache.tuscany.spi.wire.MessageImpl
The default implementation of a message flowed through a wire during an invocation
@version $Rev $Date
-
org.cometd.server.MessageImpl
-
org.exolab.jms.message.MessageImpl
This class implements the javax.jms.Message interface.
@version $Revision: 1.2 $ $Date: 2005/03/18 03:50:12 $
@author
Jim Mourikis
@see javax.jms.Message
-
org.hornetq.core.message.impl.MessageImpl
-
org.jboss.internal.soa.esb.message.format.serialized.MessageImpl
This is the basic internal core message abstraction. A message consists of the following components: Header: the header information contains information such as the destination EPR, the sender EPR, where the reply goes etc, i.e., general message-level functional information. Context: additional information to contextualise the message; for example, transaction or security data, the identity of the ultimate receiver, or HTTP-cookie like information. Body: the actual payload of the message. Fault: any fault information associated with the message. Attachment: any attachments associated with the message. Each message, once created, has a corresponding element for these 5 components. That element may be empty (NOT NULL). The object representing the element can then be used to act on the corresponding data item in the message.
@author Mark Little
-
org.jboss.internal.soa.esb.message.format.xml.MessageImpl
This is the basic internal core message abstraction. A message consists of the following components: Header: the header information contains information such as the destination EPR, the sender EPR, where the reply goes etc, i.e., general message-level functional information. Context: additional information to contextualise the message; for example, transaction or security data, the identity of the ultimate receiver, or HTTP-cookie like information. Body: the actual payload of the message. Fault: any fault information associated with the message. Attachment: any attachments associated with the message. Properties: any properties associated with the message. Each message, once created, has a corresponding element for these 5 components. That element may be empty (NOT NULL). The object representing the element can then be used to act on the corresponding data item in the message.
@author Mark Little
-
org.jboss.seam.international.status.MessageImpl
-
org.knapper.core.internal.messages.MessageImpl
-
org.mortbay.cometd.MessageImpl
-
org.springmodules.xt.model.notification.MessageImpl
{@link Message} immutable implementation.
@author Sergio Bossa
-
org.wijiscommons.ssaf.message.impl.MessageImpl
-
org.wso2.carbon.registry.social.impl.message.MessageImpl
An implementation of the {@link org.wso2.carbon.registry.social.api.message.Message} interface