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 1. XML Web Service Standards

    Given XML documents, schemas, and fragments determine whether their syntax and form are correct (according to W3C schema) and whether they conform to the WS-I Basic Profile 1.0a.

    BP 1.0 - Service Description (WSDL) - Document Structure.

    A DESCRIPTION MUST only use the WSDL "import" statement to import another WSDL description.

    To import XML Schema Definitions, a DESCRIPTION MUST use the XML Schema "import" statement.

    A DESCRIPTION MUST use the XML Schema "import" statement only within the xsd:schema element of the types section.

    A DESCRIPTION MUST NOT use the XML Schema "import" statement to import a Schema from any document whose root element is not "schema" from the namespace "http://www.w3.org/2001/XMLSchema".

    An XML Schema directly or indirectly imported by a DESCRIPTION MUST use either UTF-8 or UTF-16 encoding.

    An XML Schema directly or indirectly imported by a DESCRIPTION MUST use version 1.0 of the eXtensible Markup Language W3C Recommendation.

    CORRECT:

    						
    <definitions name="StockQuote"
          targetNamespace="http://example.com/stockquote/definitions">
          <import namespace="http://example.com/stockquote/definitions"
               location="http://example.com/stockquote/stockquote.wsdl"/>
          <message name="GetLastTradePriceInput">
             <part name="body" element="..."/>
          </message>
                      ...
    </definitions>					
    						
    					

    CORRECT:

    						
    <definitions name="StockQuote"  
       targetNamespace="http://example.com/stockquote/"
       xmlns:xsd1="http://example.com/stockquote/schemas"
               	 ...
       xmlns="http://schemas.xmlsoap.org/wsdl/">
       
       <import namespace="http://example.com/stockquote/definitions"
            location="http://example.com/stockquote/stockquote.wsdl"/>
               
       <message name="GetLastTradePriceInput">
          <part name="body" element="xsd1:TradePriceRequest"/>
       </message>
                   ...
    </definitions>						
    						
    					

    INCORRECT (imports not "wsdl" document):

    						
    <definitions name="StockQuote"
       targetNamespace="http://example.com/stockquote/definitions"
       xmlns:xsd1="http://example.com/stockquote/schemas""
               	 ...
       xmlns="http://schemas.xmlsoap.org/wsdl/">
    
       <import namespace="http://example.com/stockquote/schemas"
             location="http://example.com/stockquote/stockquote.xsd"/>
             
       <message name="GetLastTradePriceInput">
            <part name="body" element="xsd1:TradePriceRequest"/>
       </message>
                   ...
    </definitions>						
    						
    					

    A DESCRIPTION MUST specify a non-empty location attribute on the wsdl:import element.

    When they appear in a DESCRIPTION, wsdl:import elements MUST precede all other elements from the WSDL namespace except wsdl:documentation.

    When they appear in a DESCRIPTION, wsdl:types elements MUST precede all other elements from the WSDL namespace except wsdl:documentation and wsdl:import.

    CORRECT:

    						
    <definitions name="StockQuote"
          targetNamespace="http://example.com/stockquote/definitions">
    
         <import namespace="http://example.com/stockquote/base"
           location="http://example.com/stockquote/stockquote.wsdl"/>
            
          <message name="GetLastTradePriceInput">
             <part name="body" element="..."/>
          </message>
                      ...
    </definitions>						
    						
    					

    CORRECT (wsdl:types before all other elements):

    						
    <definitions name="StockQuote"  
               	 ...
       xmlns="http://schemas.xmlsoap.org/wsdl/">
    
      <types>
         <schema targetNamespace="http://example.com/stockquote/schemas"
              xmlns="http://www.w3.org/2001/XMLSchema">
               .......
         </schema>
       </types>
               
       <message name="GetLastTradePriceInput">
            <part name="body" element="tns:TradePriceRequest"/>
       </message>
                   ...
       <service name="StockQuoteService">
          <port name="StockQuotePort" binding="tns:StockQuoteSoap">
               ....
          </port>
       </service>
    </definitions>						
    						
    					

    INCORRECT (wrong position of wsdl:types element):

    						
    <definitions name="StockQuote"  
               	 ...
       xmlns="http://schemas.xmlsoap.org/wsdl/">
       
       <import namespace="http://example.com/stockquote/definitions"
             location="http://example.com/stockquote/stockquote.wsdl"/>
               
       <message name="GetLastTradePriceInput">
           <part name="body" type="tns:TradePriceRequest"/>
       </message>
                   ...
       <service name="StockQuoteService">
          <port name="StockQuotePort" binding="tns:StockQuoteSoap">
               ....
          </port>
       </service>
    
       <types>
          <schema targetNamespace="http://example.com/stockquote/schemas"
                   xmlns="http://www.w3.org/2001/XMLSchema">
               .......
          </schema>
       </types>
    </definitions>						
    						
    					

    A DESCRIPTION MUST use version 1.0 of the eXtensible Markup Language W3C Recommendation.

    DESCRIPTION MUST use either UTF-8 or UTF-16 encoding.

    The targetNamespace attribute on the wsdl:definitions element of a description that is being imported MUST have same the value as the namespace attribute on the wsdl:import element in the importing DESCRIPTION.

    A document-literal binding in a DESCRIPTION MUST, in each of its soapbind:body element(s), have at most one part listed in the parts attribute, if the parts attribute is specified.

    If a document-literal binding in a DESCRIPTION does not specify the parts attribute on a soapbind:body element, the corresponding abstract wsdl:message MUST define zero or one wsdl:parts.

    A wsdl:binding in a DESCRIPTION MAY contain soapbind:body element(s) that specify that zero parts form the soap:Body.

    An rpc-literal binding in a DESCRIPTION MUST refer, in its soapbind:body element(s), only to wsdl:part element(s) that have been defined using the type attribute.

    A MESSAGE described with an rpc-literal binding MUST NOT have the xsi:nil attribute with a value of "1" or "true" on the part accessors.

    A wsdl:message in a DESCRIPTION MAY contain wsdl:parts that use the elements attribute provided those wsdl:parts are not referred to by a soapbind:body in an rpc-literal binding.

    A document-literal binding in a DESCRIPTION MUST refer, in each of its soapbind:body element(s), only to wsdl:part element(s) that have been defined using the element attribute.

    A binding in a DESCRIPTION MAY contain soapbind:header element(s) that refer to wsdl:parts in the same wsdl:message that are referred to by its soapbind:body element(s).

    A wsdl:binding in a DESCRIPTION MUST refer, in each of its soapbind:header, soapbind:headerfault and soapbind:fault elements, only to wsdl:part element(s) that have been defined using the element attribute.

    A wsdl:binding in a DESCRIPTION SHOULD bind every wsdl:part of a wsdl:message in the wsdl:portType to which it refers to one of soapbind:body, soapbind:header, soapbind:fault or soapbind:headerfault.

    A wsdl:message in a DESCRIPTION containing a wsdl:part that uses the element attribute MUST refer, in that attribute, to a global element declaration.

    CORRECT:

    						
    <message name="GetTradePriceInput">
          <part name="body" element="tns:SubscribeToQuotes"/>       
    </message>						
    						
    					

    INCORRECT (xsd:string is not a global element):

    						
    <message name="GetTradePriceInput">
          <part name="tickerSymbol" element="xsd:string"/>
          <part name="time" element="xsd:timeInstant"/>
    </message>						
    						
    					

    INCORRECT (xsd:string is not a global element):

    						
    <message name="GetTradePriceInput">
          <part name="tickerSymbol" element="xsd:string"/>
    </message>						
    						
    					

    BP 1.0 - Service Description (WSDL) - Port Types.

    The order of the elements in the soap:body of a MESSAGE MUST be the same as that of the wsdl:parts in the wsdl:message that describes it.

    A DESCRIPTION MAY use the parameterOrder attribute of an wsdl:operation element to indicate the return value and method signatures as a hint to code generators.

    A DESCRIPTION MUST NOT use Solicit-Response and Notification type operations in a wsdl:portType definition.

    A wsdl:portType in a DESCRIPTION MUST have operations with distinct values for their name attributes.

    A wsdl:portType in a DESCRIPTION MUST be constructed so that the parameterOrder attribute, if present, omits at most 1 wsdl:part from the output message.

    A wsdl:message in a DESCRIPTION MUST NOT specify both type and element attributes on the same wsdl:part.

    BP 1.0 - Service Description (WSDL) - SOAP Binding.

    The wsdl:binding element in a DESCRIPTION MUST be constructed so that its soapbind:binding child element specifies the transport attribute.

    A wsdl:binding element in a DESCRIPTION MUST specify the HTTP transport protocol with SOAP binding. Specifically, the transport attribute of its soapbind:binding child MUST have the value "http://schemas.xmlsoap.org/soap/http".

    A wsdl:binding in a DESCRIPTION MUST use either be a rpc-literal binding or a document-literal binding.

    A wsdl:binding in a DESCRIPTION MUST use the value of "literal" for the use attribute in all soapbind:body, soapbind:fault, soapbind:header and soapbind:headerfault elements.

    A wsdl:binding in a DESCRIPTION that contains one or more soapbind:body, soapbind:fault, soapbind:header or soapbind:headerfault elements that do not specify the use attribute MUST be interpreted as though the value "literal" had been specified in each case.

    A wsdl:portType in a DESCRIPTION MAY have zero or more wsdl:bindings that refer to it, defined in the same or other WSDL documents.

    The operations in a wsdl:binding in a DESCRIPTION MUST result in wire signatures that are different from one another.

    A DESCRIPTION SHOULD NOT have more than one wsdl:port with the same value for the location attribute of the soapbind:address element.

    A document-literal binding MUST be represented on the wire as a MESSAGE with a soap:Body whose child element is an instance of the global element declaration referenced by the corresponding wsdl:message part.

    For one-way operations, an INSTANCE MUST NOT return a HTTP response that contains a SOAP envelope. Specifically, the HTTP response entity-body must be empty.

    A CONSUMER MUST ignore a SOAP response carried in a response from a one-way operation.

    For one-way operations, a CONSUMER MUST NOT interpret a successful HTTP response status code (i.e., 2xx) to mean the message is valid or that the receiver would process it.

    A document-literal binding in a DESCRIPTION MUST NOT have the namespace attribute specified on contained soapbind:body, soapbind:header, soapbind:headerfault and soapbind:fault elements.

    An rpc-literal binding in a DESCRIPTION MUST have the namespace attribute specified, the value of which MUST be an absolute URI, on contained soapbind:body elements.

    An rpc-literal binding in a DESCRIPTION MUST NOT have the namespace attribute specified on contained soapbind:header, soapbind:headerfault and soapbind:fault elements.

    A wsdl:binding in a DESCRIPTION MUST have the same set of wsdl:operations as the wsdl:portType to which it refers.

    A wsdl:binding in a DESCRIPTION MAY contain no soapbind:headerfault elements if there are no known header faults.

    A wsdl:binding in a DESCRIPTION SHOULD contain a soapbind:fault describing each known fault.

    A wsdl:binding in a DESCRIPTION SHOULD contain a soapbind:headerfault describing each known header fault.

    A MESSAGE MAY contain a fault detail entry in a SOAP fault that is not described by a wsdl:fault element in the corresponding WSDL description.

    A MESSAGE MAY contain the details of a header processing related fault in a SOAP header block that is not described by a wsdl:headerfault element in the corresponding WSDL description.

    A wsdl:binding in a DESCRIPTION MUST use the attribute named part with a schema type of "NMTOKEN" on all contained soapbind:header and soapbind:headerfault elements.

    A wsdl:binding in a DESCRIPTION MUST NOT use the attribute named parts on contained soapbind:header and soapbind:headerfault elements.

    CORRECT:

    
    <binding name="StockQuoteSoap" type="tns:StockQuotePortType">
      <soapbind:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
        <operation name="SubscribeToQuotes">
          <input message="tns:SubscribeToQuotes">
            <soapbind:body parts="body" use="literal"/>
            <soapbind:header message="tns:SubscribeToQuotes" part="subscribeheader" use="literal"/>
         </input>
       </operation>
    </binding>
    										
    					

    A wsdl:binding in a DESCRIPTION MUST have the name attribute specified on all contained soapbind:fault elements.

    In a DESCRIPTION, the value of the name attribute on a soapbind:fault element MUST match the value of the name attribute on its parent wsdl:fault element.

    ...

    ...

    ...

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