I would not use a separate class per parameter though that is a clever solution. It might hurt performance and it just feels a bit heavy. For performance, clar

I would not use a separate class per parameter though that is a clever solution. It might hurt performance and it just feels a bit heavy. For performance, clarity and reusability I would simply create a class that holds the values needed. Add an @Entity tag and now it can be used as a Hibernate persistence class too.