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
  • From a list, identify the responsibility of the bean provider and the responsibility of the container provider for a message-driven bean.

    Bean Provider responsibility

    The message-driven bean provider is responsible for providing message-driven bean class. The following are the requirements for the message-driven bean class:

    • The class MUST implement, directly or indirectly, the javax.ejb.MessageDrivenBean interface.

    • The class MUST implement, directly or indirectly, the javax.jms.MessageListener interface.

    • The class MUST be defined as public, MUST NOT be final, and MUST NOT be abstract.

    • The class MUST HAVE a public constructor that takes no arguments. The Container uses this constructor to create instances of the message-driven bean class.

    • The class MUST NOT define the finalize() method.

    • The class MUST implement the ejbCreate() method (it can be empty).

    • The message-driven bean class may have superclasses and/or superinterfaces. If the message-driven bean has superclasses, the ejbCreate method, and the methods of the MessageDrivenBean and MessageListener interfaces may be defined in the message-driven bean class or in any of its superclasses.

    • The message-driven bean class is allowed to implement other methods (for example, helper methods invoked internally by the onMessage method) in addition to the methods required by the EJB specification.

    The message-driven bean class MUST define ONE ejbCreate() method whose signature must follow these rules:

    • The method name MUST be ejbCreate.

    • The method MUST be declared as public.

    • The method MUST NOT be declared as final or static.

    • The return type MUST be void.

    • The method MUST HAVE NO arguments.

    • The throws clause MUST NOT define any APPLICATION exceptions.

    The message-driven bean class MUST define ONE onMessage method whose signature must follow these rules:

    • The method MUST be declared as public.

    • The method MUST NOT be declared as final or static.

    • The return type MUST be void.

    • The method MUST HAVE a single argument of type javax.jms.Message.

    • The throws clause MUST NOT define any APPLICATION exceptions.

    The message-driven bean class MUST define ONE ejbRemove() method whose signature must follow these rules:

    • The method name MUST be ejbRemove.

    • The method MUST be declared as public.

    • The method MUST NOT be declared as final or static.

    • The return type MUST be void.

    • The method MUST HAVE NO arguments.

    • The throws clause MUST NOT define any APPLICATION exceptions.

    Container Provider responsibility

    The container provider must support the deployment of a message-driven bean as the consumer of a JMS queue or a durable subscription.

    The container must ensure that ONLY ONE thread can be executing an instance at any time.

    The container must follow the rules with respect to transaction scoping, security checking, and exception handling.

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