An "Entity Bean" is a type of Enterprise JavaBean, a server-side Java EE component, that represents persistent data maintained in a database. An entity bean can manage its own persistence (Bean managed persistence) or can delegate this function to its EJB Container (Container managed persistence). An entity bean is identified by a primary key. If the container in which an entity bean is hosted crashes, the entity bean, its primary key, and any remote references survive the crash.
| Attributes | Values |
|---|
| rdf:type
| |
| rdfs:label
| - Entity Bean (en)
- Entity Bean (pt)
|
| rdfs:comment
| - An "Entity Bean" is a type of Enterprise JavaBean, a server-side Java EE component, that represents persistent data maintained in a database. An entity bean can manage its own persistence (Bean managed persistence) or can delegate this function to its EJB Container (Container managed persistence). An entity bean is identified by a primary key. If the container in which an entity bean is hosted crashes, the entity bean, its primary key, and any remote references survive the crash. (en)
- Um Entity Bean é um tipo de Enterprise JavaBean, um componente J2EE do lado servidor, que representa dado persistente armazenado em um banco de dados. Um entity bean pode gerenciar sua própria persistência (Bean managed persistence) ou pode delegar esta função ao seu (Container managed persistence). Um entity bean é identificado por uma chave primária. Se o recipiente no qual um entity bean está armazenado falhar, o entity bean, sua chave primária e quaisquer referências remotas sobrevivem à falha. No EJB 3.0, entity beans foram substituídos pela API Java Persistence. (pt)
|
| dcterms:subject
| |
| Wikipage page ID
| |
| Wikipage revision ID
| |
| Link from a Wikipage to another Wikipage
| |
| Link from a Wikipage to an external page
| |
| sameAs
| |
| dbp:wikiPageUsesTemplate
| |
| has abstract
| - An "Entity Bean" is a type of Enterprise JavaBean, a server-side Java EE component, that represents persistent data maintained in a database. An entity bean can manage its own persistence (Bean managed persistence) or can delegate this function to its EJB Container (Container managed persistence). An entity bean is identified by a primary key. If the container in which an entity bean is hosted crashes, the entity bean, its primary key, and any remote references survive the crash. In EJB 3.0, entity beans were superseded by the Java Persistence API (which was subsequently completely separated to its own spec as of EJB 3.1). Entity Beans have been marked as a candidate for pruning as of Java EE 6 and are therefore considered a deprecated technology. Entity Beans before EJB 2.0 should not be used in great numbers because each entity bean was in fact a RMI stub with its own RMI connection to the EJB server. Obtaining 1000 entity beans as a single operation would result in 1000 simultaneous internet connections to the RMI back-end. Since TCP/IP only supports 65536 ports you are essentially limited to using 65536 entity beans at a time. For example, if a client application wanted to monitor the state of 1024 database entries it would take 1024 entity bean references and thus 1024 RMI connections to the EJB server, the EJB server would in turn need to support all 1024 connections from each client application, and would be limited to serving at most 64 client applications at which point all further internet connections would be ignored. These limitations are impossible to overcome when using entity beans over RMI. (en)
- Um Entity Bean é um tipo de Enterprise JavaBean, um componente J2EE do lado servidor, que representa dado persistente armazenado em um banco de dados. Um entity bean pode gerenciar sua própria persistência (Bean managed persistence) ou pode delegar esta função ao seu (Container managed persistence). Um entity bean é identificado por uma chave primária. Se o recipiente no qual um entity bean está armazenado falhar, o entity bean, sua chave primária e quaisquer referências remotas sobrevivem à falha. No EJB 3.0, entity beans foram substituídos pela API Java Persistence. Antes do EJB 2.0 os entity beans não podiam ser usados em grande quantidade pois cada entity bean era de fato um com sua própria conexão RMI ao servidor EJB. Obter 1000 entity beans em uma única operação resultaria em 1000 conexões de Internet simultâneas ao back-end RMI. Como o TCP/IP suporta apenas 65536 portas você está limitado essencialmente a utilizar 65536 entity beans de uma vez. Por exemplo, se uma aplicação cliente deseja monitorar o estado de 1024 entradas de banco de dados ela pegaria 1024 referências de entity beans e assim 1024 conexões RMI ao servidor EJB, o servidor EJB por sua vez necessitaria suportar todas as 1024 conexões de cada aplicação cliente e seria limitado a servir no máximo 64 aplicações cliente de modo que todas as outras conexões seriam ignoradas. Estas limitações são impossíveis de superar quando utiliza-se entity beans sobre RMI. (pt)
|
| gold:hypernym
| |
| prov:wasDerivedFrom
| |
| page length (characters) of wiki page
| |
| foaf:isPrimaryTopicOf
| |
| is Link from a Wikipage to another Wikipage
of | |
| is Wikipage redirect
of | |
| is foaf:primaryTopic
of | |
![[RDF Data]](/fct/images/sw-rdf-blue.png)
![[cxml]](/fct/images/cxml_doc.png)
![[csv]](/fct/images/csv_doc.png)
![[text]](/fct/images/ntriples_doc.png)
![[turtle]](/fct/images/n3turtle_doc.png)
![[ld+json]](/fct/images/jsonld_doc.png)
![[rdf+json]](/fct/images/json_doc.png)
![[rdf+xml]](/fct/images/xml_doc.png)
![[atom+xml]](/fct/images/atom_doc.png)
![[html]](/fct/images/html_doc.png)