You are on page 1of 5

c 

 

g 
 g  g

î 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.1.
î £escribe the use of XML schema in J2EE Web services.

g g g  g

î List and describe the encoding types used in a SOAP message.


î £escribe the SOAP Processing and Extensibility Model.
î £escribe SOAP Message Construct and create a SOAP message that contains an
attachment.

g     g  !

î Explain the use of WS£L in Web services, including a description of WS£L's


basic elements, binding mechanisms and the basic WS£L operation types as limited
by the WS-I Basic Profile 1.1.
î £escribe how WS£L enables one to separate the description of the abstract
functionality offered by a service from concrete details of a service description such
as ³how´ and ³where´ that functionality is offered.
î £escribe the Component Model of WS£L including £escriptions, Interfaces,
Bindings, Services and Endpoints.
î £escribe the basic functions provided by the U££I Publish and Inquiry APIs to
interact with a U££I business registry.

g "# $ g
î Explain JAX-WS technology for building web services and client that
communicate using XML.
î Given a set of requirements for a Web service, such as transactional needs, and
security requirements, design and develop Web service applications that use JAX-
WS technology.
î £escribe the Integrated Stack (I-Stack) which consist of JAX-WS, JAXB, StAX,
SAAJ.
î £escribe and compare JAX-WS development approaches.
î £escribe the features of JAX-WS including the usage of Java Annotations.
î £escribe the architecture of JAX_WS including the Tools SPI that define the
contract between JAX-WS tools and Java EE.
î £escribe creating a Web Service using JAX-WS.
î £escribe JAX-WS Client Communications Models.
î Given an set of requirements, design and develop a Web service client, such as a
Java EE client and a stand-alone client, using JAX-WS.
î Given a set of requirements, create and configure a Web service client that
accesses a stateful Web service.

g %&'g()#g*)g
  # )# +
g#!

î £escribe the characteristics of REST Web Services.


î £escribe the characteristics of JSON Web Services.
î Compare SOAP web services to REST Web Services.
î Compare SOAP web services to JSON Web Services.
î £escribe the functions and capabilities of the APIs included within JAXP.
î £escribe the functions and capabilities of JAXB, including the JAXB process
flow, such as XML-to-Java and Java-to-XML, and the binding and validation
mechanisms provided by JAXB.
î Create and use a SOAP message with attachments using the SAAJ APIs.

g ,# &

î £escribe the function of JAXR in Web service architectural model, the two basic
levels of business registry functionality supported by JAXR, and the function of the
basic JAXR business objects and how they map to the U££I data structures.
î Create JAXR client to connect to a U££I business registry, execute queries to
locate services that meet specific requirements, and publish or update information
about a business service.

g -#'' g  

î Identify the characteristics of and the services and APIs included in the Java EE
platform.
î Explain the benefits of using the Java EE platform for creating and deploying
Web service applications.
î £escribe the functions and capabilities of the JAXP, £OM, SAX, StAX, JAXR,
JAXB, JAX-WS and SAAJ in the Java EE platform.
î £escribe the role of the WS-I Basic Profile when designing Java EE Web
services.

g .g /

î Explain basic security mechanisms including: transport level security, such as


basic and mutual authentication and SSL, message level security, XML encryption,
XML £igital Signature, and federated identity and trust.
î Identify the purpose and benefits of Web services security oriented initiatives and
standards such as Username Token Profile, SAML, XACML, XKMS, WS-Security,
and the Liberty Project.
î Given a scenario, implement Java EE based web service web-tier and/or EJB-tier
basic security mechanisms, such as mutual authentication, SSL, and access control.
î £escribe factors that impact the security requirements of a Web service, such as
the relationship between the client and service provider, the type of data being
exchanged, the message format, and the transport mechanism.
î £escribe WS-Policy that defines a base set of constructs that can be used and
extended by other Web services specifications to describe a broad range of service
requirements and capabilities.

g 0  1 g  


î £escribe the steps required to configure, package, and deploy Java EE Web
services and service clients, including a description of the packaging formats, such as
.ear, .war, .jar, annotations and deployment descriptor settings.
î Given a set of requirements, develop code to process XML files using the SAX,
StAX, £OM, XSLT, and JAXB APIs.
î Given an XML schema for a document style Web service create a WS£L file that
describes the service and generate a service implementation.
î Given a set of requirements, create code to create an XML-based, document style,
Web service using the JAX-WS APIs.
î Implement a SOAP logging mechanism for testing and debugging a Web service
application using Java EE Web Service APIs.
î Given a set of requirements, create code to handle system and service exceptions
and faults received by a Web services client.

g 2 g    1  /(  

î £escribe WSIT, the features of each WSIT technology and the standards that
WSIT.
î £escribe how to create a WSIT client from a Web Service £escription Language
(WS£L) file.
î £escribe how to configure Web Service providers and clients to use message
optimization.
î Create a Microsoft Windows Communication Foundation (WCF) client that
accesses a Java Web Service.
î £escribes the best practices for production and consumption of data for
interoperability between WCF Web Services and Java web service clients or between
Java WebServices and WCF Web Service clients.

g 3     

î £escribe the characteristics of a service-oriented architecture and how Web


Services fit this model.
î Given a scenario, design a Java EE Web Service using Web Services £esign
Patterns (Asynchronous Interaction, JMS Bridge, Web Service Cache, Web Serive
Broker), and Best Practices.
î £escribe how to handle the various types of return values, faults, errors, and
exceptions that can occur during a Web service interaction.
î £escribe the role that Web Services play when integrating data, application
functions, or business processes in a Java EE application.

'1   

î Given a scenario, design Web Service applications using information models that
are either procedure-style or document-style.
î £escribe the function of the service interaction and processing layers in a Web
Service.
î £esign a Web Service for an asynchronous, document-style process and describe
how to refactor a Web Service from a synchronous to an asynchronous model.
î £escribe how the characteristics, such as resource utilization, conversational
capabilities, and operational modes, of the various types of Web service clients
impact the design of a Web service or determine the type of client that might interact
with a particular service.