Return-Path: Delivered-To: apmail-ant-user-archive@www.apache.org Received: (qmail 55977 invoked from network); 6 Jan 2006 14:54:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 6 Jan 2006 14:54:56 -0000 Received: (qmail 46929 invoked by uid 500); 6 Jan 2006 14:54:50 -0000 Delivered-To: apmail-ant-user-archive@ant.apache.org Received: (qmail 46699 invoked by uid 500); 6 Jan 2006 14:54:49 -0000 Mailing-List: contact user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Users List" Reply-To: "Ant Users List" Delivered-To: mailing list user@ant.apache.org Received: (qmail 46688 invoked by uid 99); 6 Jan 2006 14:54:49 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jan 2006 06:54:49 -0800 X-ASF-Spam-Status: No, hits=1.8 required=10.0 tests=RCVD_IN_WHOIS_BOGONS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of antoine@gmx.de designates 213.165.64.21 as permitted sender) Received: from [213.165.64.21] (HELO mail.gmx.net) (213.165.64.21) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 06 Jan 2006 06:54:47 -0800 Received: (qmail invoked by alias); 06 Jan 2006 14:54:25 -0000 Received: from e180190076.adsl.alicedsl.de (EHLO [192.0.2.5]) [85.180.190.76] by mail.gmx.net (mp028) with SMTP; 06 Jan 2006 15:54:25 +0100 X-Authenticated: #22961642 Message-ID: <43BE84BD.7060105@gmx.de> Date: Fri, 06 Jan 2006 15:54:53 +0100 From: Antoine Levy-Lambert User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.11) Gecko/20050728 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ant Users List Subject: Re: Deployment to Websphere 6 References: In-Reply-To: X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Sam.Tandy@euroclear.com wrote: > >The solution of adding the Jar to the classpath works but, as you said, it >is certainly not a nice way of doing this. > >Regarding the class loader: >If I have specified the jar in the runtime classpath for ant, then call the >IBM class to stop the server from a build file supplied to ant, do they not >share a loader? > > what really matters is : - which class is instantiating the WSLauncher class ? I have stumbled against the same problem when I created an ant task which was doing some work with MQ Series across a JNDI driver. I had to put the JNDI driver in the classpath before starting ant, because the JNDI driver gets loaded by the Java Runtime, which is living in a classloader which does not know ant and certainly not the of the custom task which requires it. So my experience is that you have to put in the classpath all drivers which are loaded by the Java runtime (JNDI or JDBC drivers are the examples which come to mind). Maybe this WSLauncher class is written in such a way that it is an implementation of an interface known generally to the java runtime, and it gets instantiated with a class.forName(); This type of questions gets discussed often on the user list and on the dev list. for instance : posting by Rainer Noack with a patch http://marc.theaimsgroup.com/?l=ant-dev&m=107930923613690&w=2 bug report in bugzilla : http://issues.apache.org/bugzilla/show_bug.cgi?id=6606 Actually there is a lot of litterature concerning this issue, so I hope that the other posters who have written something about this issue do not feel offended that I do not citate them. Antoine --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@ant.apache.org For additional commands, e-mail: user-help@ant.apache.org