From: mspan at di.uoa.gr (Manos Spanoudakis)
Date: Thu, 14 Apr 2005 03:16:54 +0300
Subject: [Pljava-dev] Error message
	java.lang.ClassNotFoundException:'pljavatriggers.TestTrigger1' SOLVED
In-Reply-To: <425D98A2.5030206@mailblocks.com>
Message-ID: <000101c54087$46b4e4f0$0301a8c0@manos>


> -----Original Message-----
> From: pljava-dev-bounces at gborg.postgresql.org
> [mailto:pljava-dev-bounces at gborg.postgresql.org] On Behalf Of 
> Thomas Hallgren
> Sent: Thursday, April 14, 2005 1:10 AM
> To: Manos Spanoudakis; pljava-dev
> Subject: Re: [Pljava-dev] Error message 
> java.lang.ClassNotFoundException:'pljavatriggers.TestTrigger1'
> 
> 
> Manos,
> Take a look at your ClassNotFoundException once more. Do you see the
> leading single quote just before the name of the class? This 
> qoute stems 
> from the $body$ '...' $body$ that you're using. Essetially 
> you get two 
> single qoutes at the beginning and two at the end. PostgreSQL 
> strips the 
> outer quotes and delivers the rest to PL/Java as a method name. I 
> suggest you remove the $body$ on both sides.

The problem was with the $body$ ! Thanks !!
 
> A couple of other suggestions.
> - The CLASSPATH visible to the backend should *only* contain the
> pljava.jar. Alternatively it could be empty and instead set using 
> pljava.classpath in postgresql.conf.
> - Your execCommandLine(TriggerData) method must be static or PL/Java 
> will fail to find it.

Indeed :)

> - Don't use the sqlj schema for user defined stuff. It should be
> regarded as reserved for PL/Java. The sqlj schema as a whole will be 
> uninstalled if you redeploy pljava.
> Regards,
> Thomas Hallgren

Regards,
Manos