If you attend the survey you will get it from there.
Anyway paste it here just in case:
Sun Certified Developer for Java(TM) Web Services (310-220)
Section 1
XML Web Service Standards
Objective 1.1
Given XML documents and schemas, determine whether their syntax and form are correct (according to W3C schema) and whether they conform to the WS-I Basic Profile 1.0.
Objective 1.2
Create a Schema for an XML document used in a web service
exchange.
Objective 1.3
Describe the function of namespaces used in an XML document.
Section 2
SOAP 1.1 Web Service Standards
Objective 2.1
List and describe the encoding types used in a SOAP message.
Objective 2.2
Describe functions and use cases for SOAP message headers.
Objective 2.3
Identify and describe the function of each of the elements contained within a SOAP message, the SOAP binding to HTTP, and how to represent faults that occur when processing a SOAP message.
Objective 2.4
Create a SOAP message that contains an attachment.
Objective 2.5
Describe the restrictions placed on the use of SOAP by the WS-I Basic Profile.
Objective 2.6
Describe the function of SOAP in a web service exchange and the advantages and disadvantages of web service applications that use SOAP-based messages.
Section 3
Describing and Publishing (WSDL and UDDI)
Objective 3.1
Explain the use of WSDL in web service applications, including a description of WSDL's basic elements, binding mechanisms, and the basic WSDL operation types as limited by the WS-I basic profile.
Objective 3.2
Describe how W3C XML Schema is used to as a typing mechanism in WSDL.
Objective 3.3
Describe the purpose of each of the data structures that define a UDDI registry entry according to the limitations of the WS-I basic profile.
Objective 3.4
Describe the basic functions provided by the UDDI Publish and Inquiry APIs to interact with a UDDI business registry.
Section 4
JAX-RPC
Objective 4.1
Explain the service description model, client connection types, interaction modes, transport mechanisms/protocols, and endpoint types as they relate to JAX-RPC.
Objective 4.2
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-RPC
servlet endpoints and stateless session bean endpoints.
Objective 4.3
Given an set of requirements, design and develop a web sevice client, such as a J2EE client and a stand-alone Java client, using the appropriate JAX-RPC client connection style.
Objective 4.4
Given a set of requirements, develop and configure a web service client that accesses a stateful web service.
Objective 4.5
Explain the advantages and disadvantages of a WSDL to Java vs. a Java to WSDL development approach.
Objective 4.6
Describe the advantages and disadvantages of web service applications that use either synchronous/request response, one-way RPC, or non-blocking RPC invocation modes.
Objective 4.7
Use the JAX-RPC Handler API to create a SOAP message handler, describe the function of a handler chain, and describe the role of SAAJ when creating a message handler.
Section 5
SOAP and XML Processing APIs (JAXP, JAXB, and SAAJ)
Objective 5.1
Describe the functions and capabilities of the APIs included within JAXP.
Objective 5.2
Given a scenario, select the proper mechanism for parsing and processing the information in an XML document.
Objective 5.3
Describe 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.
Objective 5.4
Use the SAAJ APIs to create and manipulate a SOAP message.
Section 6
JAXR
Objective 6.1
Describe 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 UDDI data structures.
Objective 6.2
Use JAXR to connect to a UDDI business registry, execute queries to locate services that meet specific requirements, and publish or update information about a business service.
Section 7
J2EE Web Services
Objective 7.1
Identify the characteristics of and the services and APIs included in the J2EE platform.
Objective 7.2
Explain the benefits of using the J2EE platform for creating and deploying web service applications.
Objective 7.3
Describe the functions and capabilities of the JAXP, DOM, SAX, JAXR, JAX-RPC, and SAAJ in the J2EE platform.
Objective 7.4
Describe the role of the WS-I Basic Profile when designing J2EE web services.
Section 8
Security
Objective 8.1
Explain basic security mechanisms including: transport level security, such as basic and mutual authentication and SSL, message level security, X.509, XML encryption, XML digital signature, and federated identity and trust.
Objective 8.2
Identify the purpose and benefits of web service security oriented initiatives and standards such as Username Token Profile, SAML, XACML, XKMS, P3P, JCP, WS Security, and the Liberty Project.
Objective 8.3
Given a scenario, implement J2EE based web service web-tier and/or EJB-tier basic security mechanisms, such as mutual authentication, SSL, and access control.
Objective 8.4
Describe 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.
Section 9
Developing Web Services
Objective 9.1
Describe the steps required to configure, package, and deploy J2EE web services and service clients, including a description of the packaging formats, such as .ear, .war, .jar, deployment descriptor settings, the associated web services description file, RPC mapping files, and service reference elements used for EJB and servlet endpoints.
Objective 9.2
Given a set of requirements, develop code to process XML files using the SAX, DOM, XSLT, and JAXB APIs.
Objective 9.3
Given an XML schema for a document oriented web service create a WSDL file that describes the service and generate a service implementation.
Objective 9.4
Given a set of requirements, develop code to create an XML-based, document oriented, web service using the JAX-RPC APIs.
Objective 9.5
Implement a SOAP logging mechanism for
testing and debugging a web service application.
Objective 9.6
Given a set of requirements, develop code to handle system and service exceptions and faults received by a web services client.
Section 10
General Design and Architecture
Objective 10.1
Describe the characteristics of a service oriented architecture and how web services fits to this model.
Objective 10.2
Given a scenario, design a J2EE service using the business delegate, service locator, and/or proxy client-side design
patterns and the adapter, command, and/or fa?ade server-side patterns.
Objective 10.3
Describe alternatives for dealing with issues that impact the quality of service provided by a web service and methods to improve the system reliability, maintainability, security, and performance of a service.
Objective 10.4
Describe how to handle the various types of return values, faults, errors, and exceptions that can occur during a web service interaction.
Objective 10.5
Describe the role that web services play when integrating data, application functions, or business processes in a J2EE application.
Objective 10.6
Describe how to design a stateless service that exposes the functionality of a stateful business process.
Section 11
Endpoint Design and Architecture
Objective 11.1
Given a scenario, design web service applications using information models that are either procedure oriented or document oriented.
Objective 11.2
Describe the function of the service interaction and processing layers in a web service.
Objective 11.3
Describe the XML-related tasks performed by each phase of an XML-based, document oriented, web service application, including the consumption, business processing, and production phases.
Objective 11.4
Design a web service for an asynchronous, document-oriented process and describe how to refactor a web service from a synchronous to an asynchronous model.
Objective 11.5
Describe 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.
The BETA exam for the Web Services Developer will be from April 29 - May 23, 2004. You are viewing the actual exam objectives for the BETA exam, you can use this to prepare for the beta exam. Just a reminder that if you pass the BETA you will receive a certification kit (Certificate, Lapel Pin, ID card, Logo Agreement), but only if you have passed your Sun Certified Programmer certification (any version).
