dbTalk Databases Forums  

Java stored procedures and ASA 9 - resolved

comp.databases.sybase comp.databases.sybase


Discuss Java stored procedures and ASA 9 - resolved in the comp.databases.sybase forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
David Kerber
 
Posts: n/a

Default Java stored procedures and ASA 9 - resolved - 08-26-2004 , 03:26 PM






I had posted a bunch of plaitive cries for help with java stored
procedure in various newsgroups over the last 3 weeks or so with few
definitive answers, but I finally got it resolved. Maybe other people
can learn from our pain if they run into some of the same issues.

There were several things at work here:

1. We were trying to access the properties of java objects from ASA
stored procedures, which (I finally realized) had been deprecated; from
reading the information about the changes in ASA 9, I thought that the
only capability lost was the ability to store java objects in tables.
This necessitated adding some additional java routines to our .jar file
in order to wrap some of those objects in other function calls. Not too
difficult, but it took a while for the java programmer to figure out how
to modify the database connection code to work internal to the database,
when it was designed from the ground up to connect from outside it.

I am glad to see that the method of using java stored procs is becoming
an industry standard. Sybase's syntax and options are slightly from
some of the other vendors', but the basics are there, and there is a
load of stuff on the web for using java with DB2.


2. At times I was not using the correct options when compiling the
..java files; at first I hadn't noticed that "-target 1.1" was REQUIRED,
even when installing support for 1.3. Before that, I had been jumping
back and forth, trying different things to see what would happen.


3. (and most aggravating) I thought that I had to stop and restart
the database engine after many of the updates to my java procedures, in
order for the changes to function properly. I never figured out what
types of changes required restarting the database and which did not, but
I just got into the habit of doing it every time. It greatly slowed
down my debugging cycle, but at least I could get consistent behavior.
Then today, to my great chagrin, I discovered that simply issuing a STOP
JAVA followed by a START JAVA would have done what I needed.

--
Remove the ns_ from if replying by e-mail (but keep posts in the
newsgroups if possible).

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.