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.
An IDE is no substitute for an Intelligent Developer.
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).
Villains always have antidotes. They're funny that way. Here's an antidote disquised as a tiny ad:
Programmatically Create PDF Using Free Spire.PDF with Java