JAVAONE China 2013.

JavaOne Shanghai 2013 Call for Papers

The JavaOne Shanghai 2013 Call for Papers is now closed.

Note that the JavaOne Call for Papers tool will time you out after 15 minutes of inactivity (based on the oldest inactive tool window). Browsers supported: Internet Explorer 8 and 9, Firefox 3.6 and higher, Chrome 15.x, Safari 5.1.

Submission Information

An user account is required to submit a paper. If you do not have an account already, you will be prompted to create one before submitting. Once you create your account, you'll be taken to the login page for the Call for Papers portal. If at any time you forget your username and password, simply select the "Retrieve/Forgot Password or Username" option.


  • Every time you log into the Call for Papers portal, you will see all papers you have submitted during the 2013 Call for Papers time frame.
  • While the Call for Papers is open, you may go back and edit your previously submitted sessions.
  • At any point while submitting a session, you may stop and save your submission to complete at a later time. If you stop and save before your submission is complete (before all mandatory fields are answered), your submission will be given a status of "Partial." You can go back and edit this session while the Call for Papers is open. Note that any sessions still in “Partial” status at the time the Call for Papers closes will NOT be considered.
  • Don't forget to save after each new submission or submission update.
  • Take note of your confirmation number after each submission. If you have any questions or concerns, you will want to include that confirmation number.
  • No late submissions will be accepted.

Session Descriptor Fields

* Indicates a mandatory field

Title*: Maximum character limit is 80 characters, including spaces (approximately 12 to 17 words).

Abstract*: Maximum character limit is 750 characters, including spaces.

Presentation Summary*: For evaluation only, this is an additional description of your proposal to help the reviewers better understand your submission.

Primary Track*: Identify the content area that best describes the topic. Click here to see Primary Tracks and descriptions.

Secondary Track: If appropriate, associate an additional track to describe the topic.

Session Type*: Describes the format in which the topic will be delivered.

  • Conference Session: A 60-minute session presented by Oracle, customers, partners, developers, and/or user group members.
  • Panel: A 60-minute session presented in a panel format by multiple speakers consisting of Oracle, customers, partners, developers, and/or user group members.

Session Category*: Describes the type of information to be presented. You will be asked to select one of the following session categories:

  • Best Practices
  • Case Study
  • Product/Strategy Roadmap
  • Other

Session Category—Java Embedded for Business track*: The following categories are for the Java Embedded for Business sessions only:

  • Best Practices
  • Case Study
  • Panel

Experience Level*: Describes the assumed knowledge level needed by session attendees to understand the material that will be delivered. Choose from the following:

  • Introductory
  • Intermediate
  • Advanced

Attendee roles*: This field describes the attendee roles toward which the session is geared. You may select a maximum of two roles:

  • Architect
  • Database Administrator
  • Desktop Developer
  • Embedded Device/Systems Developer
  • Enterprise Developer
  • Executive Management (C-Level, President, Executive Vice President, Senior Vice President, or Vice President)
  • Game Developer
  • IT Manager
  • Mobile Developer
  • OS and Library Developer
  • Quality Assurance/Testing Engineer
  • Student
  • Teacher/Professor
  • User Interface Developer
  • Web Designer

Attendee roles* – Java Embedded for Business track: This field describes the attendee roles for the Java Embedded for Business sessions only. You may select a maximum of two roles:

  • Architect
  • Business Development Manager
  • CTO / CXO
  • Development Manager
  • Project Manager
  • Purchasing

Adding Participants

Each submission must have at least one speaker assigned in order to be considered.

Session Roles

Submitter Role:

  • The person submitting the session will be designated as the submitter for that session. This role is used strictly to track the session submitter. The submitter is not assumed to be the speaker of the session unless he or she assigns him or herself a speaker role.
  • The submitter will receive confirmation for the submitted session but will not receive the speaker invitation and communications after that point unless he/she is also designated as a speaker.
  • The submitter must assign at least one speaker to each session he or she enters.
  • The submitter will have the option to click a button and add him or herself as a speaker.

Speaker Role:

  • Session presenter
  • Receives all speaker communications
  • It is strongly recommended that the speaker’s biography and Twitter handle (if applicable) be included with the submission

Speaker Limit by Session Type:

  • Conference sessions:
    Maximum of 3 Oracle speakers
    Maximum of 2 non-Oracle speakers
    Can consist of any combination as long as it does not exceed 3 speakers in total
  • Panels:
    Maximum of 5 Oracle speakers
    Maximum of 4 non-Oracle speakers
    Can consist of any combination as long as it does not exceed 5 speakers in total

Session Questions

In this section, you will be asked a few questions about your session.

Review Your Session Information

In this section, you will be asked to review all the submitted information for accuracy. If you notice any incorrect or missing information, you may go back and edit. If everything looks correct, click the finish button to complete your submission. This will bring you to the confirmation page with options for next steps.