From: thhal at mailblocks.com (Thomas Hallgren)
Date: Thu, 02 Jun 2005 12:59:05 +0200
Subject: [Pljava-dev] Accessing OpenJMS Queue from PLJava
In-Reply-To: <3214799999CED64882731155DB0AAD92024BC2FD@MLSW00103>
References: <3214799999CED64882731155DB0AAD92024BC2FD@MLSW00103>
	<429EE679.7010302@mailblocks.com>
	<thhal-0+356A/NCzjY/RoYuOMUdHxOhcftH/Y@mailblocks.com>
Message-ID: <thhal-0/H56A/VCzjYFMtAJavPI2SwzsKkngM@mailblocks.com>

Nageshwar Rao wrote:

>Hi,
>Thanks for quick reply. At the first instance we did with install_jar ,we
>got the problem ,then we tried added to the classpath then also it did not
>recognize, resulting in problem.
>
>Is this right way to set the classpath or do we need to do for individual
>install_jar.
>
>sqlj.set_classpath('public','exolabcore:openjms:jms:jndi:gis:dom4j:logging')
>;
>  
>
This setting seems to be correct. There can be only one classpath per 
schema so you should never set it for each install_jar.  I'm not sure 
why this is happening. Can you try to unwind the exception and print the 
stacktrace of the innermost cause? Perhaps there's more too it than just 
a "ClassNotFoundException".

Your are 100% sure that the missing class is in the exolabcore jar?
Can you create an InitialContext in a normal Java app using the exact 
correspondance to the above classpath?

Regards,
Thomas Hallgren