Welcome to the Ranch, Volodymyr!
I gave up on Spring JDBC a long time ago. I figure that if an application is complex enough to need
Java, it's probably complex enough to justify JPA and Spring JPA is very functional and popular, especially with Hibernate JPA, but I've also used with Apache OpenJPA.
When using Spring JDBC, I'd probably have a separate DAO for Product and for ProductCategory and save/update each table using a save method in the 2 DAOs. Doing it any other way is just about the same as using JPA, but without the benefits of JPA.