Should controller creates object for service layer

Question

I'm doing backend for my Java desktop application. It's an application to manage your home budget uses H2 database. I'm still learning how to compose architecture of a program and it's my first greater project. I will create view in the future while learning JavaFX but at this stage I'm quite confused regarding connection between view-controller and service layer. I have a question about using layer architecture. I have got several layers: - controller, - service (maintain logic), - mappers, cruds etc.

As I know controller need to communicate with a service layer with a DTO (data transfer object).

While passing through service layer, out DTO object will be mapped into exact object used by CRUD (to be sent to DB). This will keep all guts inside core.

Here I've got a little problem. In which layer DTO should be created? Let's say we are going down to the application:

View -> Controller -> Service ->...

According to my informations DTO should be used between Controller and Service layer. That way can View creates DTO objects for Controller? It's a problem because at this level I don't have any kind of input validation and an application may crush (taking 'a' as a int for example). One idea was to create DTO's through static method, which would keep data validation and: returning new DTO object OR returning null if validation will fail.

I tried to be as simple as it possible. Thank you in advance for any answers and support.