If you want to do so you need to set a different strategy for the generated value. If you use a TABLE strategy (and configure it correctly) an extra table will be created that takes the sequence name and the last assigned value and will set a new id to the next value. Or you can set an id in the PrePersist JPA event. (Or even in a db trigger.)
But unless there are extremely important reasons for the constraint and the decision is made by people who fully understand the implications this manual approach to id generation has, this is a bad idea.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: @GeneratedValue with max value from table