It's not a matter of whether you're using an ORM. The @Transactional annotation invokes Spring functionality. You should be able to use it with raw JDBC (I think), but only if you're doing so via the Spring JDBC Data Manager.
Although truthfully, once you get something complex enough to require Spring, an ORM is a good investment. Hibernate can manage all but the lightest database interactions much more efficiently than you can using raw JDBC.
When it comes to destroying a civilization, gas chambers cannot hold a candle to echo chambers.
Spring offers a template JDBC Template which aims to simplify JDBC code and helps with all of those horrid checked exceptions. The template pattern is used quite a lot throughout the spring framework, so its worth knowing... However as stated above - you may just want to use JPA or even Spring Data.
The Spring Docs give a good overview of Transaction management which could be used with JDBC or JPA if the underling resource supports it (typically a database).
No matter how many women are assigned to the project, a pregnancy takes nine months. Much longer than this tiny ad:
Create Edit Print & Convert PDF Using Free API with Java