This is where you'll find all of the PDFs, slides and videos referred to within the site.
If you still have a question remaining unanswered, talk to us.
Watch the series of short videos introducing the Java Verified Submission portal.
1. Opening a Publisher Account
2. Collecting the account certificate
3. Using the pre-tester
4. Signing your app with a test signature
5. Sending your app for testing and signing
6. Signing your app as a Trusted Status developer
On December 17 2010 we announced our first developer to be granted Trusted Status - Gameloft.
View the slides and quotes relating to this announcement.
This is the final FAQ for Trusted Status - updated on November 30 2010. Trusted Status is a new status for developers announced at JavaOne on September 21 2010 by Java Verified.
Read through the FAQs and - if you're eligible - apply now by completing the online application form.
This is the full procedures document for Trusted Status, and is an elaboration of the Trusted Status FAQ document.
The document was introduced on November 30 2010.
Read this for all the information you will need to know about Trusted Status.
This document outlines the cost of Content IDs and App Audits for Trusted Status Developers at November 30 2010.
This is a sample of the Trade Mark Licensing Agreement you'll need to sign when you first register to use the Java Verified Submission Portal at https://www.pki.javaverfied.com/submission
Also see the Sample Developer Agreement.
This is a sample of the Developer Agreement you'll need to sign when you first register to use the Java Verified Submission Portal
Updated on November 30 2010 with Trusted Status information.
Also see the Sample Trade Mark Licensing Agreement.
This latest version incorporates some slight amendments to the following tests:
Removal of the need for an app flow diagram and a questionnaire section 4.1
Changes to FN8 to accommodate new phone behaviours.
Changes to FN12 for touch screen input
Changes to the exceptions for FN15
Use this online tool to select the lead Java ME device to test your apps on.
It gives you details of any supporting devices, with JSRs for all.
Search by any combination of the following, and press 'go':
This tool enables you to conveniently define the amount of testing required by your application in Java Verified ...
Here's a link to the Java Verified submission portal.
Please note: you'll only be able to access it if you're registered.
Risto from Nokia explains why this may be, through slides with a voice-over.
Why should you want an R&D Signature before you send your apps for testing?
How do you get one, and what do you do with it?
What is application signing? What indicates that an app's been signed? Where does the signature take the application?
And how do you use the Sun Java Wireless Toolkit for application signing?
Most importantly: what can do wrong, and what do you do when it happens?
What's a Publisher ID? Why do you need one? Where do you get it from, how much does it cost, and how do you install it?
Risto Helin talks about the relationship between user prompts and how Java ME applications are signed.
Also see the Signing Java ME Applications pdf.
This is where you will need to register in order to use teh submission portal. After you fill in your details you will receive a certificate that will let you securely access the submission portal. This registration and certificate will cost $200.
An overview of the to the Java Verified Submission Portal December 2013. Of interest to those already using the Submission Portal.
The Java Verified Submission Portal through which you submit your Java ME apps to get them testing and signed.