I have a doubt, is anti-pattern instantiate a Domain Object in Presentation Layer and fill the object than pass to Service Layer?

It depends on your personal view, and of course of your architecture.

If you have a rich Java client it would be a wast of ressources if you were doubling all your domain objects into so called "value objects". Why should the client not directly operate on domain objects? If you have a rich client, it will also execute some business logic, and it would be a lie to say that the client is just a silly presentation layer.

With this in mind, it is really natural if the client is instantiating business objects on user request, and only if the user presses the save button, these objects will be sent to server were they will be persisted as entities.

The whole point of a discussion like this is: it is an anti-pattern if you are doubling business logic regarding client and server classes, so that you they might differ.