Pass values between multiple forms

The problem is: settings.jsp posts to test.jsp, the user fills questions there, and a single click on test.jsp should save both the earlier settings and the questions. Replies from @javaAddict and @peter_budo noted capturing parameters and saving to the database, but did not show how to carry the settings from page one into the final save or how to do the final save safely. The options below show robust choices and a recommended flow.

Common ways to carry the settings forward

• Hidden fields: echo the settings into hidden inputs on test.jsp when settings.jsp posts there. Simple and stateless, but values live on the client and are visible/limit-sized. Not ideal for sensitive data.
• Server session: store a settings object in the HttpSession after the first submit, read it on final submit. Good for sensitive or larger data, but be mindful of memory and session timeouts.
• Persistent draft: insert a draft test row when the settings are submitted, return a draft id to test.jsp (hidden field), and attach questions to that id on final submit. Best for long flows and resume capability; requires cleanup of abandoned drafts.

Recommended practical flow

• On settings submit create either a server-side settings object in session or a draft row and return a draft id.
• On test.jsp include the draft id (if used) or keep relying on the session.
• On final submit, retrieve the saved settings, validate all inputs server-side, then perform the DB work inside a transaction: insert or update the settings row (if needed) and insert the questions, then commit. Roll back on error and remove the session attribute or mark draft completed.

Example snippets (illustrative):

// save after settings.jsp
TestSettings settings = new TestSettings(...);
session.setAttribute("testSettings", settings);

// final save (in servlet)
TestSettings settings = (TestSettings) session.getAttribute("testSettings");
Connection conn = dataSource.getConnection();
try {
  conn.setAutoCommit(false);
  // insert/update settings and insert questions using PreparedStatement
  conn.commit();
} catch (SQLException e) {
  conn.rollback();
} finally {
  conn.close();
  session.removeAttribute("testSettings");
}

Notes and cautions
Validate everything server-side, use prepared statements to avoid injection, avoid storing very large question lists in session (use draft rows or serialize compactly), enforce session timeouts, and clean up abandoned drafts. This gives an atomic, recoverable flow that answers @anuj_sharma's requirement while addressing the gaps in earlier replies.