Cannot be instantiated outside the framework, you must create new entities using World. The world creates entities via it's entity manager.
@author Arni ArentThis object cannot be directly cloned because it represents a particular instance of an entity, but a {@link BaseEntity} can be created fromthis entity by calling {@link #getState()}.
Entity node's child list represents the structure of that replacement value. Otherwise, the child list is empty. DOM Level 3 does not support editing Entity nodes; if a user wants to make changes to the contents of an Entity, every related EntityReference node has to be replaced in the structure model by a clone of the Entity's contents, and then the desired changes must be made to each of those clones instead. Entity nodes and all their descendants are readonly.
An Entity node does not have any parent.
Note: If the entity contains an unbound namespace prefix, the namespaceURI of the corresponding node in the Entity node subtree is null. The same is true for EntityReference nodes that refer to this entity, when they are created using the createEntityReference method of the Document interface.
See also the Document Object Model (DOM) Level 3 Core Specification.
The "JID"
jid = [ node "@" ] domain [ "/" resource ]
domain = fqdn / address-literal
fqdn = (sub-domain 1*("." sub-domain))
sub-domain = (internationalized domain label)
address-literal = IPv4address / IPv6address
Each allowable portion of a JID (node identifier, domain identifier, and resource identifier) MUST NOT be more than 1023 bytes in length, resulting in a maximum total size (including the '@' and '/' separators) of 3071 bytes. The following features are supported:
Entity abstract class to implement common characteristics of all concepts.
Each entity has oid and code properties. The oid property is generated by dmLite. The oid property cannot be configured. If you do not want to use the code property, do not configure it.
An entity may have a user defined id that can be simple or composite. It may contain propertie and/or neighbors. The id is configure by marking properties and/or neighbors with the unique configuration element set to true.
@author Dzenan Ridjanovic @version 2006-11-03 Entity defines an XML entity.
<xs:complexType name="EntityType" />@author grkvlt@apache.org @author Adam Lowe
Simulation, an Entity instance is returned that is associated with the delegate. Specifically, the user obtains an Entity instance from {@link Simulation#register(EntityDelegate) Simulation.register(EntityDelegate)} or from{@link Simulation#register(EntityDelegate,String) Simulation.register(EntityDelegate, String)}. Entities embody the autonomous action in a simulation. The user programs an entity's activity in the delegate implementation. The delegate uses its associated Entity instance to request services from its Simulation.
An entity can be a process entity, in which case it implements {@link ProcessDelegate ProcessDelegate}, or a scheduled entity, in which case it implements {@link EntityDelegate EntityDelegate}.
Process entities embody both proactive and reactive behavior. The {@link ProcessDelegate#agenda() ProcessDelegate.agenda()} containsthe proactive part of a Entity. The reactive behavior can be coded in action methods that are invoked by other entities.
Scheduled entities, in their {@link EntityDelegate EntityDelegate} implementations,{@link #schedule(String,double,Object[]) schedule} at leastone event in their {@link EntityDelegate#initialize() initialize} method.

Copyright © 2003-2004 The MITRE Corporation
Entity just behaves like a "bean" or "POJO" and poses very little restrictions on classes stored. Entity is the interface for any entity stored within a Database.
Advantage of using a typed data object is a) that it can be inspected to see what is in there, b) it is much easier to use the data as is intended and c) the compiler will inform you if you make a change that breaks other components depending on the Entity.
FIXME: make a common superclass for Tuple and Entity.
Entity object is used to represent the HTTP entity received from the client. The entity contains a header and body as well as the underlying Channel for the connection. If there is no body with the entity this will provide an empty body object which provides a zero length sequence of bytes.
@author Niall Gallagher
Entity declaration modeling has been left for a later Level of the DOM specification. The nodeName attribute that is inherited from Node contains the name of the entity.
An XML processor may choose to completely expand entities before the structure model is passed to the DOM; in this case there will be no EntityReference nodes in the document tree.
XML does not mandate that a non-validating XML processor read and process entity declarations made in the external subset or declared in external parameter entities. This means that parsed entities declared in the external subset need not be expanded by some classes of applications, and that the replacement value of the entity may not be available. When the replacement value is available, the corresponding Entity node's child list represents the structure of that replacement text. Otherwise, the child list is empty.
The DOM Level 2 does not support editing Entity nodes; if a user wants to make changes to the contents of an Entity , every related EntityReference node has to be replaced in the structure model by a clone of the Entity 's contents, and then the desired changes must be made to each of those clones instead. All the descendants of an Entity node are readonly.
An Entity node does not have any parent. If the entity contains an unbound namespace prefix , the namespaceURI of the corresponding node in the Entity node subtree is null . The same is true for EntityReference nodes that refer to this entity, when they are created using the createEntityReference method of the Document interface. The DOM Level 2 does not support any mechanism to resolve namespace prefixes.
The following features are supported:
Entities are intended for flat graphs. Derived classes support hierarchy (clustered graphs) by defining entities that aggregate other entities.
An Entity can contain any instance of Port. Derived classes may wish to constrain to a subclass of Port. To do this, subclasses should override the public method newPort() to create a port of the appropriate subclass, and the protected method _addPort() to throw an exception if its argument is a port that is not of the appropriate subclass.
An Entity is created within a workspace. If the workspace is not specified as a constructor argument, then the default workspace is used. The workspace is used to synchronize simultaneous accesses to a topology from multiple threads. The workspace is immutable (it cannot be changed during the lifetime of the Entity). @author John S. Davis II, Edward A. Lee @version $Id: Entity.java,v 1.125 2007/12/06 21:57:05 cxh Exp $ @since Ptolemy II 0.2 @Pt.ProposedRating Green (eal) @Pt.AcceptedRating Green (johnr) @see ptolemy.kernel.Port @see ptolemy.kernel.Relation
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |