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
  • purpose or functionality, for each of the following deployment descriptor elements: ejb-name, abstract-schema-name, ejb-relation, ejb-relationship-role, cmr-field, cmr-field-type, and relationship-role-source.

    The deployment descriptor provides the following information about the abstract persistence schemas of entity beans and their container-managed relationships:

    • An ejb-name element for each entity bean. The ejb-name MUST be a valid Java identifier and MUST be UNIQUE within the ejb-jar file.

    • An abstract-schema-name element for each entity bean. The abstract-schema-name MUST be a valid Java identifier and MUST be unique within the ejb-jar file. The abstract-schema-name element is used in the specification of EJB QL queries.

    • A set of ejb-relation elements, each of which contains a PAIR of ejb-relationship-role elements to describe the two roles in the relationship.

    • Each ejb-relationship-role element describes a relationship role: its name, its multiplicity within a relation, and its navigability. It specifies the name of the cmr-field that is used from the perspective of the relationship participant. The cmr-field-type element MUST be specified if the type of the cmr-field is java.util.Collection or java.util.Set. Each relationship role refers to an entity bean by means of an ejb-name element contained in the relationship-role-source element.

    					
    <ejb-jar>
    ...
    <enterprise-beans>
    ...
    </enterprise-beans>
    
    <relationships>
    	<!--
    	ONE-TO-MANY: Order LineItem
    	-->
    	<ejb-relation>
    		<ejb-relation-name>Order-LineItem</ejb-relation-name>
    		<ejb-relationship-role>
    			<ejb-relationship-role-name>
    				order-has-lineitems
    			</ejb-relationship-role-name>
    			<multiplicity>One</multiplicity>
    			<relationship-role-source>
    				<ejb-name>OrderEJB</ejb-name>
    			</relationship-role-source>
    			<cmr-field>
    				<cmr-field-name>lineItems</cmr-field-name>
    				<cmr-field-type>java.util.Collection</cmr-field-type>
    			</cmr-field>
    		</ejb-relationship-role>
    		<ejb-relationship-role>
    			<ejb-relationship-role-name>
    				lineitem-belongsto-order
    			</ejb-relationship-role-name>
    			<multiplicity>Many</multiplicity>
    			<cascade-delete/>
    			<relationship-role-source>
    				<ejb-name>LineItemEJB</ejb-name>
    			</relationship-role-source>
    			<cmr-field>
    				<cmr-field-name>order</cmr-field-name>
    			</cmr-field>
    		</ejb-relationship-role>
    	</ejb-relation>
    	
    	<!--
    	ONE-TO-MANY unidirectional relationship:
    	Product is not aware of its relationship with LineItem
    	-->
    	<ejb-relation>
    		<ejb-relation-name>Product-LineItem</ejb-relation-name>
    		<ejb-relationship-role>
    			<ejb-relationship-role-name>					
    				product-has-lineitems
    			</ejb-relationship-role-name>
    			<multiplicity>One</multiplicity>
    			<relationship-role-source>
    				<ejb-name>ProductEJB</ejb-name>
    			</relationship-role-source>
    			<!-- since Product does not know about LineItem
    			there is no cmr field in Product for accessing
    			Lineitem
    			-->
    		</ejb-relationship-role>
    		<ejb-relationship-role>
    			<ejb-relationship-role-name>
    				lineitem-for-product
    			</ejb-relationship-role-name>
    			<multiplicity>Many</multiplicity>
    			<relationship-role-source>
    				<ejb-name>LineItemEJB</ejb-name>
    			</relationship-role-source>
    			<cmr-field>
    				<cmr-field-name>product</cmr-field-name>
    			</cmr-field>
    		</ejb-relationship-role>
    	</ejb-relation>
    
    	<!--
    	ONE-TO-MANY: Order Customer:
    	-->
    	<ejb-relation>
    		<ejb-relation-name>Order-Customer</ejb-relation-name>
    		<ejb-relationship-role>
    			<ejb-relationship-role-name>
    				customer-has-orders
    			</ejb-relationship-role-name>
    			<multiplicity>One</multiplicity>
    			<relationship-role-source>
    				<ejb-name>CustomerEJB</ejb-name>
    			</relationship-role-source>
    			<cmr-field>
    				<cmr-field-name>orders</cmr-field-name>
    				<cmr-field-type>
    					java.util.Collection
    				</cmr-field-type>
    			</cmr-field>
    		</ejb-relationship-role>
    		<ejb-relationship-role>
    			<ejb-relationship-role-name>
    				order-belongsto-customer
    			</ejb-relationship-role-name>
    			<multiplicity>Many</multiplicity>
    			<relationship-role-source>
    				<ejb-name>OrderEJB</ejb-name>
    			</relationship-role-source>
    			<cmr-field>
    				<cmr-field-name>customer</cmr-field-name>
    			</cmr-field>
    		</ejb-relationship-role>
    	</ejb-relation>
    </relationships>
    ...
    </ejb-jar>
    					
    					

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