The current implementation of FBCallableStatement has several problems (see JDBC229, JDBC296), it is not fully JDBCcompliant and I have the feeling that it doesn't support all stored procedure options of Firebird (although that needs more research). The FBCallableStatement needs a thorough review and parts may need to be rewritten.
Modified by: @mrotteveel
Link: This issue is related to [JDBC296](https://github.com/FirebirdSQL/jaybird/issues?q=JDBC296+in%3Atitle) \[ [JDBC296](https://github.com/FirebirdSQL/jaybird/issues?q=JDBC296+in%3Atitle) \]
Modified by: @mrotteveel
Link: This issue is related to [JDBC229](https://github.com/FirebirdSQL/jaybird/issues?q=JDBC229+in%3Atitle) \[ [JDBC229](https://github.com/FirebirdSQL/jaybird/issues?q=JDBC229+in%3Atitle) \]
Modified by: @mrotteveel
Link: This issue is related to [JDBC289](https://github.com/FirebirdSQL/jaybird/issues?q=JDBC289+in%3Atitle) \[ [JDBC289](https://github.com/FirebirdSQL/jaybird/issues?q=JDBC289+in%3Atitle) \]
Submitted by: @mrotteveel
Is related to JDBC296 Is related to JDBC229 Is related to JDBC289 Relate to JDBC350 Relate to JDBC402
The current implementation of FBCallableStatement has several problems (see JDBC229, JDBC296), it is not fully JDBCcompliant and I have the feeling that it doesn't support all stored procedure options of Firebird (although that needs more research). The FBCallableStatement needs a thorough review and parts may need to be rewritten.