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
  • Describe how W3C XML Schema is used as a typing mechanism in WSDL 1.1.

    The types element encloses data type definitions that are relevant for the exchanged messages. For maximum interoperability and platform neutrality, WSDL prefers the use of XSD as the canonical type system, and treats it as the intrinsic type system.

    					
    <definitions .... >
        <types>
            <xsd:schema .... />*
        </types>
    </definitions>
    				
    					
    The XSD type system can be used to define the types in a message regardless of whether or not the resulting wire format is actually XML, or whether the resulting XSD schema validates the particular wire format. This is especially interesting if there will be multiple bindings for the same message, or if there is only one binding but that binding type does not already have a type system in widespread use.

    A DESCRIPTION MUST NOT use QName references to elements in namespaces that have been neither imported, nor defined in the referring WSDL document.

    A QName reference to a Schema component in a DESCRIPTION MUST use the namespace defined in the targetNamespace attribute on the xsd:schema element, or to a namespace defined in the namespace attribute on an xsd:import element within the xsd:schema element.

    All xsd:schema elements contained in a wsdl:types element of a DESCRIPTION MUST have a targetNamespace attribute with a valid and non-null value, UNLESS the xsd:schema element has xsd:import and/or xsd:annotation as its only child element(s).

    In a DESCRIPTION, array declarations MUST NOT extend or restrict the soapenc:Array type.

    In a DESCRIPTION, array declarations MUST NOT use wsdl:arrayType attribute in the type declaration.

    In a DESCRIPTION, array declaration wrapper elements SHOULD NOT be named using the convention ArrayOfXXX.

    A MESSAGE containing serialized arrays MUST NOT include the soapenc:arrayType attribute.

    CORRECT:

    Given the WSDL Description:

    
    <xsd:element name="MyArray1" type="tns:MyArray1Type"/>
    <xsd:complexType name="MyArray1Type">
      <xsd:sequence>
       <xsd:element name="x" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
      </xsd:sequence>
    </xsd:complexType>
    
    					
    The SOAP message would serialize as (omitting namespace declarations for clarity):
    
    <MyArray1>
      <x>abcd</x>
      <x>efgh</x>
    </MyArray1>						
    
    					

    INCORRECT (uses soapenc:arrayType attribute and soapenc:Array type):

    Given the WSDL Description:

    
    <xsd:element name="MyArray2" type="tns:MyArray2Type"/>
    <xsd:complexType name="MyArray2Type" 
     xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
      xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" >
      <xsd:complexContent>
         <xsd:restriction base="soapenc:Array">
           <xsd:sequence>
              <xsd:element name="x" type="xsd:string" 
               minOccurs="0" maxOccurs="unbounded"/>
           </xsd:sequence>
           <xsd:attribute ref="soapenc:arrayType" 
            wsdl:arrayType="tns:MyArray2Type[]"/>
       </xsd:restriction>
     </xsd:complexContent>
    </xsd:complexType>
    
    					
    The SOAP message would serialize as (omitting namespace declarations for clarity):
    
    <MyArray2 soapenc:arrayType="tns:MyArray2Type[]" >
      <x>abcd</x>
      <x>efgh</x>
    </MyArray2>							
    
    					

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