-
Control.Record
Has information on all in-and outgoing {@link Message}s. By adding a message the instance of {@link Record} gets saved to C:/Sateda/records.dat
.
@author Sebastian
-
cc.mallet.cluster.Record
-
center.task.Record
Список значений по именам и индексам Для межпоточного использования необходима синхронизация
@author Vassaev A.V.
@version 1.1 05/06/2012
-
ch.ethz.inf.vs.scandium.dtls.Record
-
com.acme.jpa.model.Record
-
com.aerospike.client.Record
Container object for records. Records are equivalent to rows.
-
com.alee.managers.language.data.Record
@author Mikle Garin
-
com.amazonaws.services.kinesis.model.Record
The unit of data of the Amazon Kinesis stream, which is composed of a sequence number, a partition key, and a data blob.
-
com.cloudera.cdk.morphline.api.Record
A record is a set of named fields where each field has a list of one or more values. A value can be of any type, i.e. any Java Object. That is, a record is a {@link ListMultimap} asin Guava’s {@link ArrayListMultimap}. Note that a field can be multi-valued and that any two records need not use common field names. This flexible data model corresponds exactly to the characteristics of the Solr/Lucene data model (i.e. a record is a SolrInputDocument). A field with zero values is removed from the record - it does not exist as such.
-
com.dbxml.db.core.data.Record
Record is a container for Key/Value pairs. Record also provides metadata for a Value stored in the database.
-
com.dotcms.repackage.org.xbill.DNS.Record
-
com.extjs.gxt.ui.client.store.Record
Records wrap model instances and provide specialized editing features, including modification tracking and editing capabilities.
Rather than editing a model from a store directly, record can be used to "buffer" any changes to the model. Changes can be "committed" or "rejected" at both the record and store level.
Record instances can be retrieved from the container store by calling @link {@link Store#getRecord(ModelData)}. To get a list of modified records call @link {@link Store#getModifiedRecords()}. Code snippet:
Record record = store.getRecord(store.getAt(0)); record.set("foo", "bar"); List<Record> modified = store.getModifiedRecords(); for (Record r : modified) { } store.commitChanges();
-
com.funambol.syncclient.sps.Record
This class implements record definition Record contain those fields:
key - record key state - record state ('N' new, 'U' update, 'D' deleted) content - record the blackberry contactuid
-
com.google.gwt.valuestore.shared.Record
Experimental API: This class is still under rapid development, and is very likely to be deleted. Use it at your own risk.
An entry in a {@link com.google.gwt.valuestore.shared.ValueStore ValueStore}.
-
com.google.refine.model.Record
-
com.google.walkaround.wave.server.auth.AccountStore.Record
-
com.gwtext.client.data.Record
Instances of this class encapsulate both record definition information, and record value information for use in Store objects, or any code which needs to access Records cached in a Store object.
@author Sanjiv Jivan
@see com.gwtext.client.data.Store
-
com.hazelcast.map.impl.record.Record
@param < V>
-
com.hazelcast.map.record.Record
-
com.hp.hpl.jena.tdb.base.record.Record
A record is pair of key and value. It may be all key, in which case value is null.
-
com.ibm.as400.access.Record
-
com.impossibl.postgres.api.data.Record
-
com.impossibl.postgres.types.PrimitiveType.Record
-
com.iqbon.spider.domain.Record
-
com.jbidwatcher.util.Record
Created by IntelliJ IDEA. User: Morgan Date: Sep 30, 2007 Time: 1:44:08 AM To change this template use File | Settings | File Templates.
-
com.jfinal.plugin.activerecord.Record
Record
-
com.mossle.form.keyvalue.Record
-
com.sencha.gxt.data.shared.Store.Record
-
com.simplegeo.client.types.Record
Representation of a record as exposed by the SimpleGeo Storage API.
@author Pranil Kanderi
-
com.smartgwt.client.data.Record
A Record is an ordinary Java class with properties that are treated as data to be displayed and edited by a {@link com.smartgwt.client.widgets.DataBoundComponent}.
{@link com.smartgwt.client.widgets.DataBoundComponent}s have a concept of named fields, where values for each field are found under the same-named property in a Record.
A Record is always an ordinary Java object regardless of how the record is loaded (static data, java server, XML web service, etc).
The concept of working with Records is common to all {@link com.smartgwt.client.widgets.DataBoundComponent}s, although individual DataBoundComponents may work with singular records ( {@link com.smartgwt.client.widgets.form.DynamicForm}) or may work with lists ( {@link com.smartgwt.client.widgets.grid.ListGrid}), trees ( {@link com.smartgwt.client.widgets.tree.TreeGrid}), or cubes (CubeGrid) of records.
Individual DataComponents may also look for special properties on Records which control styling or behavior for those records, such as {@link com.smartgwt.client.widgets.grid.ListGrid#setRecordEditProperty(String)}
-
com.tririga.pub.workflow.Record
-
com.webdeninteractive.xbotts.Mapping.compiler.Record
This would be called Element, but it would collide with w3c Element all over the place
@author bmadigan
-
com.workingdogs.village.Record
A Record represents a row in the database. It contains a collection of
Values which are the individual contents of each column in the row.
@author
Jon S. Stevens
@version $Revision: 568 $
-
com.xensource.xenapi.PIF.Record
-
com.xensource.xenapi.VGPUType.Record
-
de.fzi.herakles.commons.log.Record
-
edu.stanford.nlp.util.logging.Redwood.Record
-
edu.wpi.first.smartdashboard.state.Record
Represents a field sent by a robot
-
eu.stratosphere.types.Record
Record is the basic data record that flows between functions in a Stratosphere program. The record is a tuple of arbitrary values. It implements a sparse tuple model, meaning that the record can contain many fields which are actually null and not represented in the record. It has internally a bitmap marking which fields are set and which are not.
For efficient data exchange, a record that is read from any source holds its data in serialized binary form. Fields are deserialized lazily upon first access. Modified fields are cached and the modifications are incorporated into the binary representation upon the next serialization or any explicit call to the {@link #updateBinaryRepresenation()} method.
IMPORTANT NOTE: Records must be used as mutable objects and be reused across user function calls in order to achieve performance. The record is a heavy-weight object, designed to minimize calls to the individual fields' serialization and deserialization methods. It holds quite a bit of state consumes a comparably large amount of memory (> 200 bytes in a 64 bit JVM) due to several pointers and arrays.
This class is NOT thread-safe!
-
fr.dyade.aaa.jndi2.impl.Record
-
gr.ekt.bte.core.Record
-
hu.sztaki.ilab.longneck.Record
Basic data element with change history, containing a set of named fields.
@author Péter Molnár
-
io.fathom.cloud.compute.api.os.model.Record
-
io.fathom.cloud.openstack.client.dns.model.Record
-
it.eng.spagobi.tools.dataset.common.datastore.Record
@author Angelo Bernabeiangelo.bernabei@eng.it
-
javax.resource.cci.Record
@version $Rev: 46019 $ $Date: 2004-09-14 03:56:06 -0600 (Tue, 14 Sep 2004) $
-
javolution.util.FastCollection.Record
-
javolution.util.stripped.FastCollection.Record
-
jxl.read.biff.Record
-
ke.go.moh.oec.adt.data.Record
This class represents a record of data. A record of data is composed of a {@link PrimaryKey} and one or more {@link Cell}s.
@date Apr 21, 2012
@author Gitahi Ng'ang'a
-
net.sf.cb2java.data.Record
-
net.sf.jpluck.palm.Record
Interface for Palm CookieStore records. Implementations must provide the record's ID and write its data.
Records are added to a {@link net.sf.jpluck.palm.Database}. The database iterates through these records and writes their IDs and data to a PDB.
@see net.sf.jpluck.palm.Database
-
no.priv.garshol.duke.Record
Represents a record, which may be a single source record from a data source, or a record created from merging data from many records.
-
org.apache.avro.generic.GenericData.Record
-
org.apache.blur.thrift.generated.Record
Records contain a list of columns, multiple columns with the same name are allowed.
-
org.apache.camel.component.stax.model.Record
-
org.apache.empire.data.Record
The record interface provides methods used for updating data.
A object implementing the record interface is essentially a so called "dynamic bean".
This interface inherits from RecordData which provides further data access methods.
The Record interface is implemented by the class {@link org.apache.empire.db.DBRecord}
-
org.apache.flink.types.Record
The Record represents a multi-valued data record and forms the base of the "Record API" The record is a tuple of arbitrary values. It implements a sparse tuple model, meaning that the record can contain many fields which are actually null and not represented in the record. It has internally a bitmap marking which fields are set and which are not.
For efficient data exchange, a record that is read from any source holds its data in serialized binary form. Fields are deserialized lazily upon first access. Modified fields are cached and the modifications are incorporated into the binary representation upon the next serialization or any explicit call to the {@link #updateBinaryRepresenation()} method.
IMPORTANT NOTE: Records must be used as mutable objects and be reused across user function calls in order to achieve performance. The record is a heavy-weight object, designed to minimize calls to the individual fields' serialization and deserialization methods. It holds quite a bit of state consumes a comparably large amount of memory (> 200 bytes in a 64 bit JVM) due to several pointers and arrays.
This class is NOT thread-safe!
-
org.apache.hadoop.metrics2.util.MetricsCache.Record
JVM and logging related metrics. Mostly used by various servers as a part of the metrics they export.
-
org.apache.jackrabbit.core.journal.Record
Record interface.
-
org.apache.jute.Record
Interface that is implemented by generated classes.
@author Milind Bhandarkar
-
org.apache.jute_voltpatches.Record
Interface that is implemented by generated classes.
-
org.apache.poi.hslf.record.Record
This abstract class represents a record in the PowerPoint document. Record classes should extend with RecordContainer or RecordAtom, which extend this in turn.
@author Nick Burch
-
org.apache.poi.hssf.record.Record
Title: Record Description: All HSSF Records inherit from this class. It populates the fields common to all records (id, size and data). Subclasses should be sure to validate the id, Company:
@author Andrew C. Oliver
@author Marc Johnson (mjohnson at apache dot org)
@author Jason Height (jheight at chariot dot net dot au)
@version 2.0-pre
-
org.apache.qpid.server.store.Transaction.Record
-
org.apache.tuscany.sca.itest.Record
@version $Rev$ $Date$
-
org.apache.webbeans.telephone.entity.Record
-
org.apache.xindice.core.data.Record
Record is a container for Key/Value pair. Record also provides metadata for a Value stored in the database.
-
org.cipango.dns.record.Record
-
org.company.recordshop.domain.Record
A Record is a representation of a physical medium containing one or more musical compositions.
@author Generated by Mod4j BusinessDomain DSL
-
org.errai.samples.serialization.client.model.Record
-
org.errai.samples.serialization.client.shared.Record
-
org.fao.oaipmh.responses.Record
-
org.geotools.data.shapefile.shp.ShapefileReader.Record
-
org.goobi.production.importer.Record
-
org.gwtoolbox.widget.client.data.Record
@author Uri Boness
-
org.jboss.as.console.client.model.Record
@author Heiko Braun
@date 7/12/11
-
org.jboss.wsf.spi.management.recording.Record
@author alessio.soldano@jboss.com
@since 8-Dec-2007
-
org.jclouds.logging.BufferLogger.Record
-
org.jclouds.rackspace.clouddns.v1.domain.Record
@author Everett Toews
-
org.jooq.Record
A wrapper for database result records returned by {@link SelectQuery}
@author Lukas Eder
@see SelectQuery#getResult()
-
org.kiji.proto.test.TestProtocolBuffers.Record
-
org.kitesdk.morphline.api.Record
A record is a set of named fields where each field has a list of one or more values. A value can be of any type, i.e. any Java Object. That is, a record is a {@link ListMultimap} asin Guava’s {@link ArrayListMultimap}. Note that a field can be multi-valued and that any two records need not use common field names. This flexible data model corresponds exactly to the characteristics of the Solr/Lucene data model (i.e. a record is a SolrInputDocument). A field with zero values is removed from the record - it does not exist as such.
-
org.lilyproject.repository.api.Record
A Record is the core entity managed by the {@link Repository}.
A Record can be instantiated via {@link Repository#newRecord() Repository.newRecord} or retrieved via{@link Repository#read(RecordId) Repository.read}. As all entities within this API, records are dumb data objects.
All Record-related CRUD operations are available on the {@link Repository} interface:{@link Repository#create(Record) Create}, {@link Repository#read(RecordId) Read}, {@link Repository#update(Record) Update}, {@link Repository#delete(RecordId) Delete}.
A Record object is not necessarily a representation of a complete record. When {@link Repository#read(RecordId,java.util.List) reading}a record, you can specify to only read certain fields. Likewise, when {@link Repository#update(Record) updating}, you only need to put the fields in this object that you want to be updated. But it is not necessary to remove unchanged fields from this object, the repository will compare with the current situation and ignore unchanged fields.
Since for an update, this object only needs to contain the fields you want to update, fields that are not in this object will not be automatically removed from the record. Rather, you have to say explicitly which fields should be deleted by adding them to the {@link #getFieldsToDelete() fields-to-delete} list. If thefields-to-delete list contains field names that do not exist in the record, then these will be ignored upon update, rather than causing an exception.
The {@link RecordType} and its version define the schema of the record. As is explained in more detail inLily's repository model documentation, a record has a pointer to three (possibly) different record types, one for each scope.
-
org.marc4j.marc.Record
Represents a MARC record.
@author Bas Peters
@version $Revision: 1.12 $
-
org.milyn.flatfile.Record
-
org.mule.module.db.integration.model.Record
-
org.nfctools.ndef.Record
-
org.nutz.dao.entity.Record
记录对象
@author zozoh(zozohtnt@gmail.com)
-
org.ofbiz.datafile.Record
Record
-
org.onebusaway.transit_data.model.realtime.CurrentVehicleEstimateQueryBean.Record
-
org.openoffice.xmerge.converter.palm.Record
Contains the raw bytes for a Record
in a PDB.
Note that it is not associated with a Record
number or ID.
@author Akhil Arora, Herbie Ong
@see PalmDocument
@see PalmDB
-
org.prevayler.demos.scalability.Record
-
org.smpp.smscsim.util.Record
The class Record
represents a set of Attribute
s. It's used in Table
class. It can represent various types of data, e.g. user settings, config parameters etc. When used in Table
, different records might have different attributes -- attributes with different names.
@author Logica Mobile Networks SMPP Open Source Team
@version $Revision: 1.2 $
@see Table
@see Attribute
-
org.sonatype.tests.http.server.jetty.behaviour.Record
-
org.tmatesoft.hg.repo.HgStatusCollector.Record
-
org.tmatesoft.hg.test.LogOutputParser.Record
-
org.xbill.DNS.Record
A generic DNS resource record. The specific record types extend this class. A record contains a name, type, class, and rdata.
@author Brian Wellington
-
pt.opensoft.dbaccess.Record
This class implements the funcionality assciated with a record (line) of a table.
-
pt.opensoft.field.Record
-
ru.vsu.amm.domain.Record
-
se.kb.oai.pmh.Record
-
sos.hostware.Record
-
whitedb.holder.Record