-
com.amazonaws.services.simpleemail.model.Body
Represents the body of the message. You can specify text, HTML, or both. If you use both, then the message should display correctly in the widest variety of email clients.
-
com.apitrary.api.annotation.Body
-
com.badlogic.gdx.physics.box2d.Body
A rigid body. These are created via World.CreateBody.
@author mzechner
-
com.cloudcontrolled.api.annotation.Body
-
com.dgwave.osrs.jaxb.Body
@author Akber Choudhry
-
com.feth.play.module.mail.Mailer.Mail.Body
-
com.github.sommeri.less4j.core.ast.Body
-
com.ning.http.client.Body
A request body.
-
com.sissi.protocol.message.Body
@author kim 2013-11-1
-
com.vtence.molecule.Body
-
eas.simulation.spatial.sim2D.physicalSimulation.physicsEngine.net.phys2d.raw.Body
A single body within the physics model
@author Kevin Glass
-
global.Message.Body
-
info.textgrid.lab.noteeditor.mei2013.Body
3.org/2001/XMLSchema}anyType"> <group ref="{http://www.music-encoding.org/ns/mei}model.mdivLike" maxOccurs="unbounded"/> <attGroup ref="{http://www.music-encoding.org/ns/mei}att.declaring.attributes"/> <attGroup ref="{http://www.music-encoding.org/ns/mei}att.common.attributes"/> </restriction> </complexContent> </complexType>
-
jabber.client.Body
3.org/XML/1998/namespace}lang"/> </extension> </simpleContent> </complexType>
-
jinngine.physics.Body
A body is a rigid body entity, that is animated according to the laws of Newton. A body can have one or more geometry instances attached, and these define its final mass and inertia properties.
-
my.home.dsl.deepClone.Body
A representation of the model object '
Body'.
The following features are supported:
- {@link my.home.dsl.deepClone.Body#getPackageConfig Package Config}
- {@link my.home.dsl.deepClone.Body#getCloners Cloners}
@see my.home.dsl.deepClone.DeepClonePackage#getBody()
@model
@generated
-
net.javlov.world.Body
-
net.phys2d.raw.Body
A single body within the physics model
@author Kevin Glass
-
net.sourceforge.align.util.bind.tmx.Body
3.org/2001/XMLSchema}anyType"> <sequence> <element ref="{}tu" maxOccurs="unbounded" minOccurs="0"/> </sequence> </restriction> </complexContent> </complexType>
-
net.sourceforge.segment.srx.io.bind.Body
3.org/2001/XMLSchema}anyType"> <sequence> <element ref="{http://www.lisa.org/srx20}languagerules"/> <element ref="{http://www.lisa.org/srx20}maprules"/> </sequence> </restriction> </complexContent> </complexType>
-
org.apache.camel.Body
-
org.apache.ecs.html.Body
This class creates a <BODY></BODY> tag.
@version $Id: Body.java,v 1.4 2003/04/27 09:20:40 rdonkin Exp $
@author
Stephan Nagy
@author
Jon S. Stevens
-
org.apache.james.mime4j.dom.Body
A body of an MIME entity (as defined in RFC 2045).
A body can be a {@link Message}, a {@link Multipart} or a {@link SingleBody}. This interface should not be implemented directly by classes other than those.
-
org.apache.james.mime4j.message.Body
Encapsulates the body of an entity (see RFC 2045).
@version $Id: Body.java,v 1.4 2004/10/04 15:36:43 ntherning Exp $
-
org.apache.maven.doxia.site.decoration.Body
-
org.apache.maven.plugins.changes.model.Body
-
org.apache.soap.Body
A Body
object represents the contents and semantics of a <SOAP-ENV:Body>
element.
@author Matthew J. Duftler (duftler@us.ibm.com)
@author Sanjiva Weerawarana (sanjiva@watson.ibm.com)
-
org.apache.tapestry.html.Body
The body of a Tapestry page. This is used since it allows components on the page access to an initialization script (that is written the start, just inside the <body> tag). This is currently used by {@link Rollover} and {@link Script}components. [
Component Reference]
@author Howard Lewis Ship
@version $Id: Body.java 244170 2005-03-17 08:54:30Z pferraro $
-
org.apache.wicket.markup.html.border.Body
This is a simple Container component which can be used to build Border like components.
Example:
Panel Markup: .. <div wicket:id="myPanel"> My Panels body </div> .. Panel associated Markup: <wicket:panel> .. <div wicket:id="myBody"/> .. </wicket:panel> Panel Java code: class MyPanel extends Panel { .. public MyPanel(String id) { add(new Body("myBody", this); } .. }
There can be any number of containers between the Panel and Body. You must only remember to provide the correct markup provider to the Body.
@author Juergen Donnerstag
-
org.asynchttpclient.Body
A request body.
-
org.camunda.bpm.model.cmmn.impl.instance.Body
@author Roman Smirnov
-
org.docx4j.wml.Body
3.org/2001/XMLSchema}anyType"> <sequence> <group ref="{http://schemas.openxmlformats.org/wordprocessingml/2006/main}EG_BlockLevelElts" maxOccurs="unbounded" minOccurs="0"/> <element name="sectPr" type="{http://schemas.openxmlformats.org/wordprocessingml/2006/main}CT_SectPr" minOccurs="0"/> </sequence> </restriction> </complexContent> </complexType>
-
org.eclipse.handly.model.impl.Body
-
org.jboss.identity.federation.org.xmlsoap.schemas.soap.envelope.Body
3.org/2001/XMLSchema}anyType"> <sequence> <any/> </sequence> </restriction> </complexContent> </complexType>
-
org.jboss.soa.esb.message.Body
The message body holds arbitrary information which represents the payload as far as clients and services are concerned. A body may contain: (i) a byte array for arbitrary data. How that array is interpreted by the service is implementation specific and outside the scope of the ESB to enforce. (ii) a list of Objects of arbitrary types. How these objects are serialized to/from the message body when it is transmitted is up to the specific Object type. The plan is to add support for various TYPES of Object and the message implementation will use external adapters to externalize/internalize the Objects. Currently we only support Serializable objects. Given that there are attachments, properties, byte arrays and named objects, you may be wondering where should you put your payload? The answer is fairly straightforward: As a service developer, you define the contract that clients use in order to interact with your service. As part of that contract, you will specific both functional and non-functional aspects of the service, e.g., that it is an airline reservation service (functional) and that it is transactional (non-functional). You'll also define the operations (messages) that the service can understand. As part of the message definition, you stipulate the format (e.g., Java Serialized message versus XML) and the content (e.g., transaction context, seat number, customer name etc.) When defining the content, you can specify where in the Message your service will expect to find the payload. That can be in the form of attachments, specific named objects (even the default named object if you so wish), or the byte array. It is entirely up to the service developer to determine. The only restrictions are that objects and attachments must be globally uniquely named, or one service (or Action) may inadvertently pick up a partial payload meant for another if the same Message Body is forwarded across multiple hops. As a service users, you obtain the contract definition about the service (e.g., through UDDI or out-of-band communication) and this will define where in the message the payload must go. Information placed in other locations will likely be ignored and result in incorrect operation of the service. Note, in order to maintain loose coupling, services should not expose any backend implementation choices. As such you should try to avoid sending Java Serialized instances within the Body where possible because it does limit your future choices on service implementation to Java and potentially specific versions of Java.
-
org.jbox2d.dynamics.Body
A rigid body. These are created via World.createBody.
@author Daniel Murphy
-
org.mime4j.message.Body
-
org.newdawn.fizzy.Body
A single body in the world. A body holds a shape which collide with the rest of the world. It also holds properties about the shapes once they have been created. The generic T represents the type of the userData.
@author kglass
-
org.openhab.binding.netatmo.internal.messages.MeasurementResponse.Body
-
org.opensaml.ws.soap.soap11.Body
SOAP 1.1 Body.
-
org.rendersnake.tag.Tag.Body
-
org.simpleframework.http.message.Body
The Body
interface is used to represent the body of a HTTP entity. It contains the information that is delivered with the request. The body is represented by a stream of bytes. In order to access the entity body this interface provides a stream which can be used to read it. Also, should the message be encoded as a multipart message the individual parts can be read using the Attachment
instance for it.
@author Niall Gallagher
-
org.w3._2003._05.soap_envelope.Body
An implementation of the model object '
Simple'.
The following features are implemented:
- {@link org.w3.xlink.impl.SimpleImpl#getActuate Actuate}
- {@link org.w3.xlink.impl.SimpleImpl#getArcrole Arcrole}
- {@link org.w3.xlink.impl.SimpleImpl#getHref Href}
- {@link org.w3.xlink.impl.SimpleImpl#getRole Role}
- {@link org.w3.xlink.impl.SimpleImpl#getShow Show}
- {@link org.w3.xlink.impl.SimpleImpl#getTitle Title}
- {@link org.w3.xlink.impl.SimpleImpl#getType Type}
- {@link org.w3.xlink.impl.SimpleImpl#getContents Contents}
@generated
-
org.xmlsoap.schemas.soap.envelope.Body
3.org/2001/XMLSchema}anyType"> <sequence> <any/> </sequence> </restriction> </complexContent> </complexType>
-
railo.transformer.bytecode.Body
Body tag (Statement collector)
-
rocks.xmpp.extensions.httpbind.model.Body
-
soot.Body