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
  • Client View of a Session Bean

    A client locates a session bean’s home interface using JNDI. For example, the remote home interface for the Cart session bean can be located using the following code segment:

    				
    Context initialContext = new InitialContext(); 
    CartHome cartHome = (CartHome)javax.rmi.PortableRemoteObject.narrow(
    	initialContext.lookup(“java:comp/env/ejb/cart”),
    	CartHome.class);
    				

    If the Cart session bean provides a local client view instead of a remote client view and CartHome is a local home interface, this lookup might be as follows:

    				
    Context initialContext = new InitialContext();
    CartHome cartHome = (CartHome)
    	initialContext.lookup(“java:comp/env/ejb/cart”);
    				

    A client can pass a remote home object reference to another application. The receiving application can use the home interface in the same way that it would use a remote home object reference obtained via JNDI.

    A client can pass a local home object reference to another application through its local interface. A local home object reference cannot be passed as an argument or result of a method on an enterprise bean’s remote home or remote interface.

    The REMOTE HOME interface allows a client to do the following:

    • Create a new session object.

    • Remove a session object (using bean's HANDLE).

    • Get the javax.ejb.EJBMetaData interface for the session bean. The javax.ejb.EJBMetaData interface is intended to allow application assembly tools to discover information about the session bean, and to allow loose client/server binding and client-side scripting.

    • Obtain a handle for the REMOTE home interface. The home handle can be SERIALIZED and written to stable storage. Later, possibly in a different JVM, the handle can be deserialized from stable storage and used to obtain back a reference of the remote home interface.

    public interface EJBHome extends Remote {
    	EJBMetaData getEJBMetaData() throws RemoteException;
    	HomeHandle getHomeHandle() throws RemoteException;
    	void remove(Handle handle) throws RemoteException, 
    		RemoveException;
    	void remove(Object primaryKey) throws RemoteException, 
    		RemoveException; // only Entity EJB !!!
    }	
    					

    The LOCAL HOME interface allows a local client to do the following:

    • Create a new session object.

    public interface EJBLocalHome {
    	void remove(Object primaryKey) throws RemoveException, 
    			EJBException;  // only Entity EJB !!!
    }					
    					

    EJBMetaData and HomeHandle are ONLY accessible for REMOTE HOME interfaces.

    EJBHome interface extends Remote (marker) interface.

    Session bean can be removed ONLY using it's handle (remote view ONLY), since it does not have primary key.

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