Review the Starter Code
Checkout and Review the Starter Code
Set up a local copy of the project:
- In Canvas, find Graded Assignment #4: TechJobs (Persistent Edition) and click on the starter code repo link. Fork the repository to your personal profile, copy the repo’s URL for cloning, and open up IntelliJ. Refer back to the instructions from assignment0 for more details.
- Launch the application (via the Gradle pane, Tasks > Application > bootRun) to make sure it starts up properly. Then shut it down.
- The tests for this assignment are set up the same way as for Tech Jobs OO .
You won’t be able to run your application or the tests yet. If you try to do so, you’ll see a host of errors relating to the Spring Data annotations and classes. Some of these have already been used in the code, but the dependency that includes them has not yet been declared. That will be one of your tasks. You’ll need to complete Part 1 before you can run the application and view it in a browser.
That said, it’s a good idea to scan the classes and templates even before you’re able to execute
bootRun. Take a gander at the
Job class. It will look somewhat similar to the model in
Tech Jobs (MVC Edition)
, with a few key differences.
You’re no longer using a csv file to load job data, instead, we’ll be creating new Job objects via a user form. The Job data will be stored in a MySQL database that you’ll setup in Part 1 of this assignment.
As you explore
the starter code, you’ll notice that the
JobField abstract class is no longer present. Your task for
Part 2 is to complete the work to persist some of the classes.
You’ll do this for
Skill classes, as well as
Job class will also look different from how you have last seen it. In
Part 3 and
, you’ll add object relational mapping on the
Job class by refactoring the
In your IntelliJ project, you’ll see an empty file in the root directory called
queries.sql. After completing the
Java updates for parts 1, 2, 3, and 4, we ask you to test your application updates with SQL statements.
Since you are entering your own data, the queries we ask you to write will return unique result sets. For example, if you haven’t entered any data yet, there may be an empty result set. However, as the architect of the database, you have the knowledge to write the appropriate queries nonetheless.