Exercise Tuesday

Goal: Continue to practice creating web applications in Spark. We'll also integrate the additional concepts and functionalities we learned about last night, including POST requests, and saving data to sessions, if you’d like to explore sessions. Each project should have back-end logic with full test coverage, and a functioning Spark front-end user interface. Work through the lessons slowly and thoroughly, as they contain many foundational concepts and approaches you’ll be expected to know for the rest of Java Unit and your time at Epicodus.

Then, get some practice under your belt so you feel well prepared for this week’s independent project. Instead of rushing through the prompts, instead focus on picking on that “Spark’s” (geddit) your interest and build it out as much as possible.

Warm Up


  • What is a session?
  • What is the difference between a GET and POST request?
  • When should you use a POST request?
  • When should you use a GET request?
  • How does Spark know where to send information from a form?

Code


Epicodus Blog

Then, work through the following lessons from last night's homework to begin creating a Blog with your partner.

CD Organizer

Make a program for users to catalog and organize their CDs (or another object specific to a hobby you and your partner share)! Users should be able to create a new entry containing details about an object, then see all entries listed out on a dedicated page in the application.

Kombucha Tracker

You work for a hip startup that keeps a rotation of Kombucha’s on tap. You’ve agreed to create a Kombucha tracker where colleagues can submit their notes on which Kombucha’s they liked and didn’t like.

Resume Creator

Create a website where users can fill out a form describing each past job they've held. Job attributes could include position title, company name, company location, a brief description, and dates of employment.

Then, one area in the application should display all jobs the user has entered, similar to a resume.

Peer Code Review


  • Code has proper indentation and spacing
  • Variable names are descriptive
  • Tests are in place for back-end logic. All tests pass.
  • Spark set up is complete
  • Spark routes process GET and POST requests/responses successfully.
  • Application works as expected.