Originally posted by Davide Pierri:
I send my voucher last week too, i've received only this respnse
(with the object line: Out of Office AutoReply: SCMAD Voucher):
We are in the office Mon-Fri, 7:30AM to 4:00PM, CST.
Upload/download requests are addressed every other day.
If you sent a certificate inquiry between the dates of January 20 to current, we are addressing these inquiries on an individual basis in the order in which they were received.
All other email issues are answered in the order they are received. Please do not send multiple emails concerning the same requsest.
We appreciate your business and value your feedback, and will respond to your email as soon as we are able.
Anybody received the same response?
Dear Sun Certified Mobile Application Developer candidate,
Congratulations, you are now confirmed for the Sun Certified Mobile Application Developer for the Java 2 Platform, Micro Edition, Version 1.0 beta exam. Please read this e-mail carefully.
Your electronic voucher number is:
Voucher #: XXXXXXXXX
Expires: February 25, 2004
This voucher number is only valid for the 311-110, Sun Certified Mobile Application Developer for the Java 2 Platform, Micro Edition, Version 1.0 beta exam from February 5, 2004 through February 25, 2004.
If you do not take the exam by February 25, 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 email@example.com and we will arrange to give the voucher number to another candidate.
Do not lose this number. On February 3, 2004, Prometric will begin registration or the 311-110 beta exam. You will need to call the Prometric registration center in your region (see list at the bottom of this email to register for the location, date and time you wish to take the exam. They will ask for the voucher number above at that time.
You will have four (4) hours to complete 160 questions, the time allotted will give you time to respond to all questions and provide your valuable comments while taking the exam. Your comments will be reviewed when selecting the final questions for the exam.
Around the end of April, after the final exam has been published, you will receive confirmation of your passing or failing score. You will NOT be able to find out your score before that time, so please do not send us a request for your score. Once the scoring is complete you will be able to view your score in the Certification database, www.galton.com/~sun. You will also receive a score report in the mail from Prometric. If you have passed the exam you will receive your "certification kit" once your score has been entered into the database.
Please see the Sun Certified Mobile Application Developer for the Java 2 Platform, Micro Edition, Version 1.0 beta testing objectives listed at the bottom of this mail.
Prometric Regional Service Centers:
AUSTRIA 0800 298 582
BELGIUM 0800 1 7414
DENMARK 802 40 830
EASTERN EUROPE 31 320 23 9895
FINLAND 800 93343
FRANCE 0800 807790
GERMANY 0800 1839 708
IRELAND 1800 626104
ISRAEL 800 9242007
ITALY 800 878441
NETHERLANDS 0800 0227584
NORWAY 800 30164
POLAND 00800 4411321
PORTUGAL 0800 203589
RUSSIA 737 0881
SOUTH AFRICA 0800 575575
SPAIN 900 151210
SWEDEN 0200 117023
SWITZERLAND 0800 556 966
TURKEY 800 44914073
UNITED KINGDOM 0800 592 873
* China: Please contact your local Prometric Testing Center. Prometric Testing Centers are listed at www.2test.com
HONG KONG 800-96-6375
* India: Please contact your local Prometric Testing Center. Prometric Testing Centers are listed at www.2test.com
NEW CALEDONIA 61-2-9903-9730
NEW ZEALAND 0800-44-1603
* Pakistan: Please contact your local Prometric Testing Center. Prometric Testing Centers are listed at www.2test.com
PAPAU NEW GUINEA 61-2-9903-9730
* South Korea: Please contact your local Prometric Testing Center. Prometric Testing Centers are listed at www.2test.com
* Sri Lanka: Please contact your local Prometric Testing Center. Prometric Testing Centers are listed at www.2test.com
LATIN AMERICA 1-443-751-4300 ... OR E-MAIL: LAMREGS@PROMETRIC.COM
If you have any questions please email firstname.lastname@example.org
Thank you again for your participation!
* * * * * * * * * * * * * * * * * * * * * * * *
Sun Certified Mobile Application Developer for the Java 2 Platform, Micro Edition,
Version 1.0 Testing Objectives
* * * * * * * * * * * * * * * * * * * * * * * *
Section 1: JTWI (JSR 185) and Overview / JTWI-compliant Wireless Applications
1.1 Identify the goals and characteristics of the JTWI specification (JSR 185), including the mandatory specifications, conditionally required specifications, and the minimum configuration. Compare the relationship and differences between JTWI and other wireless Java technologies.
1.2 Develop portable applications that are compatible with the requirements and restrictions an application programmer must adhere to, in order to ensure compatibility with a JTWI-compliant device, including resource minimums (eg. standard-size application), clock resolution, and the use of preferred MIME names as applicable to CLDC 1.0/1.1, MIDP 2.0, WMA 1.1, and MMAPI 1.1).
Section 2: CLDC (1.0 / 1.1)
2.1 Identify correct and incorrect statements or examples about the requirements and scope of the CLDC specification, including the differences between 1.0 and 1.1.
2.2 Describe the ways in which a CLDC virtual machine does and does not adhere to the Java Language Specification (JLS) and the Java Virtual Machine specification.
2.3 Identify correct and incorrect statements or examples about CLDC classes including those derived from J2SE, and the CLDC-specific classes, including identifying which core J2SE classes are NOT included in CLDC, or have different behaviors (example: java.lang.String, io classes, etc.)
2.4 Given the differences and limitations of exception/error handling with CLDC devices, handle exceptions correctly.
2.5 Wirte code that effectively manages memory / garbage collection.
Section 3: Security (both CLDC and MIDP)
3.1 Given a set of requirements, design and build applications given CLDC-specified application-level security, including the sandbox model.
3.2 Identify correct and incorrect statements or examples about untrusted MIDlet suites.
3.3 Explain trusted MIDlet suite security authorization and permissions, including the process for MIDlet suite signing.
3.4 Explain requirements and process of using X.509 PKI authentication for MIDlet suites.
Section 4: Networking
4.1 Write code using the Generic Connection framework specified by CLDC, recognizing its characteristics, use, classes, and interfaces. This may include identification of the class hierarchy and relationships of the Generic Connection framework.
4.2 Write code for MIDP 2.0 networking, and issues and limitations related to HTTP, HTTPS, and TCP/IP sockets and Datagrams, recognizing which connections are required and which are optional, as well as comparing the issues related to TCP/IP and UDP Datagrams.
4.3 Write code using the MIDP 2.0 classes in the javax.microedition.io package, including code that correctly opens, closes, and uses a network connection, using the implications of network blocking operations, scheme, connection number limitations, and character encoding.
4.4 Given a problem scenario, troubleshoot networking issues for MIDP 2.0.
Section 5 -- Application Model /Delivery / Lifecycle / Provisioning
5.1 Explain the specification guarantees for: browsing for MIDlet suites, transferring MIDlet suites, using HTTP, push registries, basic authentication, installing and updating MIDlet suites, invoking MIDlet suites, and deleting MIDlet suites.
5.2 Identify correct and incorrect statements or examples about the MIDP application model, including: the MIDP execution environment, MIDlet suites, MIDlet suite packaging (including the manifest and the application descriptor), discovering available services on the device, discovering which version of MIDP/CLDC is on the device.
5.3 Develop applications that correctly reflect a MIDlet's application lifecycle, including: the purpose of the MIDlet class, communication with the application management software, platform request API, valid MIDlet states and transitions, and the behavior that should and should NOT be implemented within different lifecycle methods (including the constructor).
5.4 Deploy a MIDP 2.0 application with the correct use of JAD files and manifests.
5.5 Given an installation failure, analyze the problem, , and develop possible resolutions.
5.6 Given a set of requirements, develop applications that correctly implement MIDP 2.0 support for delayed or scheduled activities using timers and background threads.
Section 6: MIDP Persistent Storage
6.1 Develop code that correctly implements handling, sharing and removing RecordStores within MIDlet suites.
6.2 Develop code that correctly implements adding, retrieving, modifying, and deleting individual records in a RecordStore, and converting RecordStore record data to and from byte arrays, and that reflects performance implications.
6.3 Identify correct and incorrect statements or examples about filtering, comparing, event listening, and enumerating records in a RecordStore.
Section 7 -- Push Registry
7.1 Explain MIDP 2.0 Push Registry benefits, and limitations, and describe its use in applications.
7.2 Develop applications that correctly use MIDP 2.0 Push Registry including discovery, dynamic vs. static, and recognizing the types of connections that can and cannot be accepted.
Section 8 -- MIDP UI API
8.1 Given a scenario, develop MIDP 2.0-compliant user interfaces, recognizing portability requirements and limitations (e.g. double-buffering not guaranteed), and performance issues (e.g. using inner classes, freeing memory buffers, etc.).
8.2 Discuss the MIDP user interface high-level API including concurrency, portability, structure of the API, and interplay with the application manager.
8.3 Explain the MIDP user interface low-level API including font support, repainting, and coordinate system.
8.4 Given a set of requirement, develop interactive MIDP 2.0 user interface code with proper event-handling (including both the high-level and low-level APIs, repainting and threading issues).
8.5 Identify correct and incorrect statements or examples about the classes (including the class hierarchy) within the javax.microedition.lcdui package.
8.6 Compare and contrast high-level and low-level APIs, including layout techniques.
8.7 Explain requirements, issues, class hierarchy, and relationships between items and screens.
Section 9: MIDP Game API
9.1 Given a scenario, develop code using the MIDP Game API package to improve performance and reduce application size.
9.2 Compare and contrast the use of MIDP's GameCanvas class vs. the MIDP low-level Canvas.
9.3 Given a set of requirements, develop code using MIDP's LayerManager class.
9.4 Given a set of requirements, develop code using MIDP's Layer, Sprite and TiledLayer classes.
Section 10: Media using MIDP 2.0 and the Mobile Media API 1.1 (MMAPI)
10.1 Given a set of requirements, develop code using MMAPI's support for tone generation.
10.2 Given a set of requirements, develop code that correctly uses MIDP support for sound including audio playback, tone generation, media flow controls (start, stop, etc.), media type controls (volume, tone), and media capabilities using "Manager", "Player", and "Control" objects, recognizing the difference between required vs. optional features.
10.3 Develop code that correctly uses MMAPI support for playback and recording of media, including the use of the "DataSource", "Player", and "Manager" objects, support for audio and video capture and playback, system properties queries, recognizing the difference between required and optional features.
10.4 Identify correct and incorrect statements or examples about the media class hierarchies in both MIDP 2.0 and MMAPI 1.1.
Section 11: Wireless Messaging API 1.1 (WMA)
11.1 Describe the WMA's basic support for sending and receiving messages, and the Generic Connection Framework.
11.2 Explain the WMA's support for SMS and Cell Broadcast capabilities.
11.3 Identify correct and incorrect statements or examples about WMA including the WMA addressing scheme, client vs. server connections, WMA-related exceptions, WMA-related security issues, message size limitation, message creation, sending, synchronous vs. asynchronous message receipt, and the relationship between WMA and Push Registry.