With experience implementing the update feature for

categories, it's now your turn to implement the update feature for gifs.

Here's what you'll need to do.

Change the timely view for the gif form to allow it to be used for updating as well.

Add new controller methods for capturing requests to the update form and

to the update submission.

But note, since updating only the description using the same form would

require advance controller logic and validation code that's outside the scope

of this course, for now we'll require that anytime users want to update a gif,

they'll need to upload a new photo as well.

Okay, when I say code, pause the video and craft your solution.

When you're done, un-pause, and I'll show you mine.

Ready, set, code!

All right, so you've taken a stab at your own update implementation and

maybe even succeeded.

Either way, let me show you how I did it.

Let's start with a Thymeleaf template which I'm in right now that is

the gifform.html file.

Up here in the h2 element I've added this th:text attribute

which references a heading model attribute.

This is so that I can have a variable heading here that either says edit or

upload, depending on the situation in which we're using it.

And if I scroll down a bit,

you can see that I did the same thing with the submit button.

I reference the model attribute I have named, submit.

Going back up there are two more things that I want to point out here.

First, is another variable item.

That is an action model attribute that will have to have been added and

that allows me to use different form actions depending on whether we want

to post to the URI that's used to add a new gif or update an existing gif.

And finally I added this hidden ID here so

that if we are editing an existing gif, that numeric value can be preserved.

Now, because all of these model attributes will have to have been added by

the controller, let me switch there now to show you how I did that part.

This is all very similar to what we did for updating categories so

it should look familiar.

Now, here in the formNewGif method and the formEditGif methods,

you can see where I've added those attributes.

One for action, one for heading, and one for submit.

Now moving on from the controller methods that render the gif form form,

let me quickly mention the listGifs method.

And that is up towards the top.

In fact it is the first method here.

If we'd even like to see the list of gifs without typing the URLs ourselves in

the browser we need to fetch the list of gifs.

Now notice how I replaced what was previously a new empty array list here.

I've replaced it with a call to the gif services, findAll method.

And just like that, the explorer link in the browser will work.

If I switch over here, I can look at the explorer link and

I see the one gif that I I've uploaded into my application.

Which then allows us to access the detail page by clicking on it and it's this page

that contains that Edit link which gives us the Edit form for our gifs.

Okay cool.

Now let me show you one other change that was needed.

So I'm going to go back to IntelliJ and I am going to open the GifDao|mp|.

Just like we saw with categories, if we had continued using the hibernateSessions

save method, we'd always get new entities when we called the Dao's

save method even when we were updating a gif entity.

So I've changed that here to be saveOrUpdate and there you have it.

If your solution wasn't quite working, go ahead and

bring yours up to speed before moving on.

I should note here that if you added JPA validation annotations to the give class,

you'd want to make sure that the gif parameter in the controller's add gif and

update gif methods were annotated with the valid annotation and that you check for

validation errors with a binding result object just like we did for categories.