Neoview Guide to Stored Procedures in Java (R2.5)

overwrite the original JAR file on the Neoview platform. For more information, see “Upload a
JAR File” (page 33).
If you upload a JAR file that contains an SPJ method that has a different class name, method
name, or signature than the original SPJ method, you must drop the SPJ from the database before
uploading the JAR file. After uploading the JAR file, re-create the SPJ in the database. You must
also drop and re-create an SPJ to rename the procedure or change the SQL parameter definitions
even if the Java bytecode remains the same. For more information, see “Create a Procedure”
(page 37) and “Drop a Procedure” (page 40).
When you update an SPJ or its Java bytecode, try to avoid making those changes when client
applications are actively calling the SPJ. If you update an SPJ or its Java bytecode when a client
application is calling the SPJ, the CALL statement might return wrong or inconsistent data to
the calling application. Therefore, schedule a time to update the SPJ or its Java bytecode when
client applications are not actively calling the SPJ.
Altering an SPJ and Its Java Bytecode 45