Hi Everyone,
I have some details for the beta!!!

Please remember that you MUST be a Sun Certified Programmer (any version) to
receive a FREE Voucher.

The beta will be held from January 19 - February 6. There are 160 questions
and I have alloted 5 hours total for responding to each questions and
receiving your valuable comments. That way you have enough time to assess
each question.

You will need to send an email to SunCert@prometric.com to request your
voucher. You will receive an email from Prometric with your free voucher
number, who to contact to sign up and objectives.

As all beta exams, if you do not take the exam by Februray 6, 2004, the
voucher will expire and you will have to purchase a voucher in order to take
the live exam. This voucher is NOT transferable and cannot be used by anyone
but yourself. Should you not be able to take the Beta, please contact
SunCert@prometric.com and they will arrange to give the voucher number to
another candidate.

Remember, if you pass the beta you will receive your Certifate Kit.

If you have any questions, please feel free to email directly at
evelyn.cartagena@sun.com.

Thank you all so much!

[editado]

Que prova é essa?
A nova versão da de Web Component Developer com J2EE 1.4?

Pois é, qual prova?

Vou mandar um email dizendo o quê?

[quote]There are 160 questions
and I have alloted 5 hours total for responding to each questions and
receiving your valuable comments[/quote]

160 Questões??? :shock:

é para a nova certificação de J2ME :slight_smile:
vi uma noticia sobre isto no JavaRanch :slight_smile:

[quote=“Bani”]Que prova é essa?
A nova versão da de Web Component Developer com J2EE 1.4?[/quote]

É sim!!! :smiley:

Testing Objectives:

1 The Servlet Technology Model

1.1 For each of the HTTP Methods (such as GET, POST, HEAD, and so on)
describe the purpose of the method and the technical characteristics of the
HTTP Method protocol, list triggers that might cause a Client (usually a Web
browser) to use the method; and identify the HttpServlet method that
corresponds to the HTTP Method.

1.2 Using the HttpServletRequest interface, write code to retrieve HTML form
parameters from the request, retrieve HTTP request header information, or
retrieve cookies from the request.

1.3 Using the HttpServletResponse interface, write code to set an HTTP
response header, set the content type of the response, acquire a text stream
for the response, acquire a binary stream for the response, redirect an HTTP
request to another URL, or add cookies to the response.

1.4 Describe the purpose and event sequence of the servlet life cycle: (1)
servlet class loading, (2) servlet instantiation, (3) call the init method,
(4) call the service method, and (5) call destroy method.

1.5 Objective deleted.

2 The Structure and Deployment of Web Applications

2.1 Construct the file and directory structure of a Web Application that may
contain (a) static content, (b) JSP pages, © servlet classes, (d) the
deployment descriptor, (e) tag libraries, (d) JAR files, and (e) Java class
files; and describe how to protect resource files from HTTP access.

2.2 Describe the purpose and semantics for each of the following deployment
descriptor elements: error-page, init-param, mime-mapping, servlet,
servlet-class, servlet-mapping, servlet-name, and welcome-file.

2.3 Construct the correct structure for each of the following deployment
descriptor elements: error-page, init-param, mime-mapping, servlet,
servlet-class, servlet-mapping, servlet-name, and welcome-file.

2.4 Explain the purpose of a WAR file and describe the contents of a WAR
file, how one may be constructed.

3 The Web Container Model

3.1 For the ServletContext initialization parameters: write servlet code to
access initialization parameters; and create the deployment descriptor
elements for declaring initialization parameters.

3.2 For the fundamental servlet attribute scopes (request, session, and
context): write servlet code to add, retrieve, and remove attributes; given
a usage scenario, identify the proper scope for an attribute; and identify
multi-threading issues associated with each scope.

3.3 Describe the Web container request processing model; write and configure
a filter; create a request or response wrapper; and given a design problem,
describe how to apply a filter or a wrapper.

3.4 Describe the Web container life cycle event model for requests,
sessions, and web applications;create and configure listener classes for
each scope life cycle; create and configure scope attribute listener
classes; and given a scenario, identify the proper attribute listener to
use.

3.5 Describe the RequestDispatcher mechanism; write servlet code to create a
request dispatcher; write servlet code to forward or include the target
resource; and identify and describe the additional request-scoped attributes
provided by the container to the target resource.

4 Session Management

4.1 Write servlet code to store objects into a session object and retrieve
objects from a session object.

4.2 Given a scenario describe the APIs used to access the session object,
explain when the session object was created, and describe the mechanisms
used to destroy the session object, and when it was destroyed.

4.3 Using session listeners, write code to respond to an event when an
object is added to a session, and write code to respond to an event when a
session object migrates from one VM to another.

4.4 Given a scenario, describe which session management mechanism the Web
container could employ, how cookies might be used to manage sessions, how
URL rewriting might be used to manage sessions, and write servlet code to
perform URL rewriting.

5 Web Application Security

5.1 Based on the servlet specification, compare and contrast the following
security mechanisms: (a) authentication, (b) authorization, © data
integrity, and (d) confidentiality.

5.2 In the deployment descriptor, declare a security constraint, a Web
resource, the transport guarantee, the login configuration, and a security
role.

5.3 Compare and contrast the authentication types (BASIC, DIGEST, FORM, and
CLIENT-CERT); describe how the type works; and given a scenario, select an
appropriate type.

6 The JavaServer Pages (JSP) Technology Model

6.1 Identify, describe, or write the JSP code for the following elements:
(a) template text, (b) scripting elements (comments, directives,
declarations, scriptlets, and expressions), © standard and custom actions,
and (d) expression language elements.

6.2 Write JSP code that uses the directives: (a) ‘page’ (with attributes
‘import’, ‘session’, ‘contentType’, and ‘isELIgnored’), (b) ‘include’, and
© ‘taglib’.

6.3 Write a JSP Document (XML-based document) that uses the correct syntax.

6.4 Describe the purpose and event sequence of the JSP page life cycle: (1)
JSP page translation, (2) JSP page compilation, (3) load class, (4) create
instance, (5) call the jspInit method, (6) call the _jspService method, and
(7) call the jspDestroy method.

6.5 Given a design goal, write JSP code using the appropriate implicit
objects: (a) request, (b) response, © out, (d) session, (e) config, (f)
application, (g) page, (h) pageContext, and (i) exception.

6.6 Configure the deployment descriptor to declare one or more tag
libraries, deactivate the evaluation language, and deactivate the scripting
language.

6.7 Given a specific design goal for including a JSP segment in another
page, write the JSP code that uses the most appropriate inclusion mechanism
(the include directive or the jsp:include standard action).

7 Building JSP Pages Using the Expression Language (EL)

7.1 Given a scenario, write EL code that accesses the following implicit
variables including pageScope, requestScope, sessionScope, and
applicationScope, param and paramValues, header and headerValues, cookie,
initParam and pageContext.

7.2 Given a scenario, write EL code that uses the following operators:
property access (the . operator), collection access (the [] operator).

7.3 Given a scenario, write EL code that uses the following operators:
aritmetic operators, relational operators, and logical operators.

7.4 Given a scenario, write EL code that uses a function; write code for an
EL function; and configure the EL function in a tag library descriptor.

8 Building JSP Pages Using Standard Actions

8.1 Given a design goal, create a code snippet using the following standard
actions: jsp:useBean (with attributes: ‘id’, ‘scope’, ‘type’, and ‘class’),
jsp:getProperty, and jsp:setProperty (with all attribute combinations).

8.2 Given a design goal, create a code snippet using the following standard
actions: jsp:include, jsp:forward, and jsp aram.

9 Building JSP Pages Using Tag Libraries

9.1 For a custom tag library or a library of Tag Files, create the ‘taglib’
directive for a JSP page.

9.2 Given a design goal, create the custom tag structure in a JSP page to
support that goal.

9.3 Given a design goal, use an appropriate JSP Standard Tag Library (JSTL
v1.1) tag from the “core” tag library.

10 Building a Custom Tag Library

Old objective 10.1 deleted.

10.1 Describe the semantics of the “Classic” custom tag event model when
each event method (doStartTag, doAfterBody, and doEndTag) is executed, and
explain what the return value for each event method means; and write a tag
handler class.

10.2 Using the PageContext API, write tag handler code to access the JSP
implicit variables and access web application attributes.

10.3 Given a scenario, write tag handler code to access the parent tag and
an arbitrary tag ancestor.

10.4 Describe the semantics of the “Simple” custom tag event model when the
event method (doTag) is executed; write a tag handler class; and explain the
constraints on the JSP content within the tag.

10.5 Describe the semantics of the Tag File model; describe the web
application structure for tag files; write a tag file; and explain the
constraints on the JSP content in the body of the tag.

11 J2EE Patterns

11.1 Given a scenario description with a list of issues, select a pattern
that would solve the issues. The list of patterns you must know are:
Intercepting Filter, Model-View-Controller, Front Controller, Service
Locator, Business Delegate, and Transfer Object.

11.2 Match design patterns with statements describing potential benefits
that accrue from the use of the pattern, for any of the following patterns:
Intercepting Filter, Model-View-Controller, Front Controller, Service
Locator, Business Delegate, and Transfer Object.