Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <50DDD177.5030007@sbcglobal.net>
Date: Fri, 28 Dec 2012 09:05:59 -0800
From: Katherine Marsden <kmarsdenderby@sbcglobal.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Derby Discussion <derby-user@db.apache.org>
Subject: Re: Problem with User Defined Type - External Java Class
References: <1356584652035-126086.post@n7.nabble.com>
 <50DC7D0B.1030306@oracle.com>
 <CAGJuDTh2fCMsYx6YE3vGvzhGuMHNyDVzneNmG_4=WiLKPqif-Q@mail.gmail.com>
In-Reply-To: 
 <CAGJuDTh2fCMsYx6YE3vGvzhGuMHNyDVzneNmG_4=WiLKPqif-Q@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 12/27/2012 8:38 PM, kosurusekhar wrote:
> Hi Rick,
> The jar is included in classpath, but while mapping the Store proc 
> parameters it is throwing error, in another store proc i created 
> object for my UDT class, there it created an object. I am suspecting 
> that mapping the variables done by another ClassLoader.
>
If you don't have control over the ClassLoader classpath, one option 
might be to install the jar in the database.
https://builds.apache.org/job/Derby-docs/lastSuccessfulBuild/artifact/trunk/out/devguide/cdevdeploy30736.html