Are You Recruiter/Hiring Manager?
Cloud-based Candidate Screening | Online Tests
PMP 1600 Questions
PMP 1600 Questions
1600 PMP mock questions 1400 CAPM mock questions 800 SCJP 6 mock questions 600 OCAJP 7 mock questions 590 OCPJP 7 mock questions 556 SCWCD 5 mock questions 500 OCEJWCD 6 mock questions pdfDownload (java,struts, hibernet etc)

Tutorial Home

Hibernate

  • Advantage of Hibernate over JDBC
  • Hibernate Setup with an web Application
  • First Hibernate Application
  • Hibernate mapping with Database TABLE
  • Hibernate Data Type-Java Data Type - SQL Data Type mapping
  • One to Many Relation in Hibernate
  • One to Many Relation in Hibernate bi-directional
  • Many to Many Relation in Hibernate
  • HQL: The Hibernate Query Language
  • Criteria Queries
  • Criteria Queries : Equal (eq), Not Equal(ne), Less than (le), greater than (gt),greater than or equal(ge) and Ordering the results
  • Criteria Queries: And OR conditions
  • Hibernate generator to generate id (primary key)
  • prevent concurrent update in Hibernate,slate object updatation in Hibernate,version checking in Hibernate

    Struts


  • Model View Controller (MVC)
  • Model View Controller (MVC)
  • Struts Flow-How Struts Works?
  • Struts Tutorial - Struts Setup- First Struts Action class setup
  • Message Resources
  • Validation Framework
  • Validation Framework-client side
  • ForwardAction
  • IncludeAction
  • DispatchAction
  • LookupDispatchAction
  • DynaActionForm
  • DynaActionForm
  • Struts Tutorial - Mutli-click prevention using struts tokens-Prevent Duplicate Submission
  • Logic Iterate Map and List

    JSP


  • JSP Tutorial
  • Introduction to JSP
  • JSP Comments
  • JSP Syntax
  • JSP Scripting Elements :Scriptlet, expression, declaration
  • JSP Directives
  • implicit objects in JSP
  • JSP Actions
  • Introduction to JSP
  • jsp:useBean
  • The jsp:setProperty Action
  • The jsp:getProperty Action
  • Introduction to JSP

    Spring


  • Spring Tutorial
  • Introduction to Spring
  • Benefits of Using Spring Framework
  • Inversion of Control in Spring
  • Introduction to BeanFactory
  • Dependency Injection in Spring
  • Collections Setter Injection
  • Bean Scopes in Spring
  • Spring IOC Setup Step by Step
  • Bean Lifecycle in Spring
  • ApplicationContext
  • MessageSources in Spring
  • Web Spring MVC framework
  • Developing Your First Spring Web Application
  • Developing Your Second Spring Web Application with Spring Form
  • Developing Your First Spring Web Application with Spring Validation Framework with Code Example
  • Spring integration with Hibernate
  • Chapter 6. Component Contract for Container-Managed Persistence (CMP)

    Identify correct and incorrect statements or examples about the entity bean provider's view and programming contract for CMP, including the requirements for a CMP entity bean.

    An entity bean implements an object view of a business entity or set of business entities stored in an underlying database or implemented by an existing enterprise application

    An entity bean with container-managed persistence (CMP) typically consists of its entity bean class; a component interface which defines its client view business methods; a home interface which defines the create, remove, home, and finder methods of its client view; and its abstract persistence schema as specified in the deployment descriptor (META-INF/ejb-jar.xml).

    A client of an entity bean can control the lifecycle of a bean by using the bean’s HOME interface and can manipulate the bean as a business entity by using the methods defined by its COMPONENT interface. The home and component interfaces of a bean define its CLIENT VIEW.

    The bean provider MUST observe the following programming contract when defining an entity bean class that uses container-managed persistence (CMP):

    • The Bean Provider must define the entity bean class as an ABSTRACT class. The container provides the implementation class that is used at RUNTIME.

    • The container-managed persistent fields and container-managed relationship fields MUST NOT be defined in the entity bean class. From the perspective of the Bean Provider, the container-managed persistent (CMP) fields and container-managed relationship (CMR) fields are VIRTUAL fields only, and are accessed through get and set accessor methods. The IMPLEMENTATION of the container-managed persistent fields and container-managed relationship fields is supplied by the Container.

    • The container-managed persistent (CMP) fields and container-managed relationship (CMR) fields MUST be specified in the deployment descriptor (DD) using the cmp-field and cmr-field elements respectively. The names of these fields MUST be valid Java identifiers and must begin with a LOWERCASE letter.

    • The Bean Provider MUST define the accessor methods for the container-managed persistent fields and container-managed relationship fields as get and set methods, using the JavaBeans conventions. The IMPLEMENTATION of the accessor methods is supplied by the Container.

    • The accessor methods MUST be public, MUST be abstract, and MUST bear the name of the container-managed persistent field (cmp-field) or container-managed relationship field (cmr-field) that is specified in the deployment descriptor (DD), and in which the first letter of the name of the cmp-field or cmr-field has been UPPERCASED and prefixed by “get” or “set”.

    • The accessor methods for a container-managed relationship (CMR) field MUST be defined in terms of the LOCAL interface of the related entity bean.

    • The accessor methods for container-managed relationship fields for one-to-many or many-to-many relationships MUST utilize one of the following Collection interfaces: java.util.Collection or java.util.Set. The Collection interfaces used in relationships are specified in the deployment descriptor. The IMPLEMENTATION of the collection classes used for the container-managed relationship fields is supplied by the Container.

    • An entity bean local interface type (or a collection of such) CAN be the type of a cmr-field. An entity bean local interface type (or a collection of such) CAN NOT be the type of a cmp-field.

    • The accessor methods for the container-managed relationship fields MUST NOT be exposed in the REMOTE interface of an entity bean.

    • The LOCAL interface types of the entity bean and of related entity beans MUST NOT be exposed through the REMOTE interface of the entity bean.

    • The collection classes that are used for container-managed relationships MUST NOT be exposed through the REMOTE interface of the entity bean.

    • Once the primary key for an entity bean has been set, the Bean Provider MUST NOT attempt to change it by use of set accessor methods on the primary key cmp-fields. The Bean Provider SHOULD therefore NOT expose the SET accessor methods for the primary key cmp-fields in the component interface of the entity bean.

    • The Bean Provider MUST ensure that the Java types assigned to the cmp-fields are restricted to the following: Java primitive types and Java serializable types.

    The information you are posting should be related to java and ORACLE technology. Not political.