Calling plsql from java when you need to pass boolean parameter is tricky and as Oracle suggests you can:
For example, to wrap a stored procedure that uses PL/SQL booleans, you can create a stored procedure that takes a character or number from JDBC and passes it to the original procedure as BOOLEAN, or, for an output parameter, accepts a BOOLEAN argument from the original procedure and passes it as a CHAR or NUMBER to JDBC. Similarly, to wrap a stored procedure that uses PL/SQL records, you can create a stored procedure that handles a record in its individual components (such as CHAR and NUMBER). To wrap a stored procedure that uses PL/SQL tables, you can break the data into components or perhaps use Oracle collection types.
http://www.oracle.com/technetwork/database/enterprise-edition/jdbc-faq-090281.html#34_05
Ok it works, but what if I have to use http://docs.spring.io/spring/docs/1.2.9/api/org/springframework/jdbc/object/StoredProcedure.html object? Passing just Types.BOOLEAN throws java.sql.SQLException and claims wrong type. Do I still need wrapper function?
