Line: 10 to 10 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Added: | ||||||||
> > | To learn more: http://java.sun.com/j2ee/tutorial/doc/Entity.html , but the Account entity bean doesn't work with jboss because it holds the Connection instead of closing it for each method. | |||||||
Changed: | ||||||||
< < | To learn more: http://java.sun.com/j2ee/tutorial/doc/Entity.html | |||||||
> > | Although it's important to understand how all the various interfaces work, most of the code generation can be automated by a tool called EJBDoclet which is a clever little javadoc plugin. | |||||||
-- TobyCabot - 03 Apr 2001 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > | An Entity Bean is persistent. The persistence can be CMP (container-managed persistence) or BMP (bean-managed persistence). Each bean has a primary key which is basically analogous to a rdbms primary key in that it uniquely identifies a specific bean. A bean can have transactional properties that allow it to participate in transactions, which are usually managed by the container.
A bean must have:
|