Actually it did change the behavior, .class and source were out of synch. I also had to put the bean for the procedure before the derby initializer bean in the Spring config so the app context is set before the temp db is intialized and the proc called. There are still problems with executing the prepared stmt, but I appear to be in the ballpark. Home run tomorrow...
-----Original Message----- From: Clark, Harry Sent: Mon 6/21/2010 4:11 PM To: Derby Discussion Cc: Subject: RE: Procedure issue One issue is that the method has to be static, but making it static didn't change the behavior. -----Original Message----- From: Clark, Harry Sent: Mon 6/21/2010 12:27 PM To: [email protected] Cc: Subject: Procedure issue I can't get a procedure to execute. It's in the database, and the code is in the classpath. But it doesn't get called. I'm probably overlooking something simple.
<<winmail.dat>>
