Hi Peter,
Thanks for your answer. And sorry for late reply, I was on vacation.
Peter Reilly wrote:
The task does strange things with the classloader.
My advice would be to use fork="yes" unless there
is a reason not to.
Yes, I see. fork="yes" solved the problem.
As regards the exception y
The task does strange things with the classloader.
My advice would be to use fork="yes" unless there
is a reason not to.
As regards the exception you are seeing, this is as far
as I can see behaviour as designed.
If one gives a classpath to the task, the classname
*must* be in the classpath, fo
I suggest you pull Ant out of the equation and get the client to run using
Java on the command line. First run the jar_attilla_client target that
run_attilla_client depends on. If you can do this successfully, then go back
to the Ant script and see if there are any noticeable differences between
t
Hi Andrew,
thanks for the reply. I've tried putting the oc4jclient.jar on
the classpath (see below) but still to no avail. I'm running the script
independently of oc4j i.e. running it from Ant on my hard drive.
Below is are the relevant bits of the script.
Thanks again for your hel
Are you using the ANT_HOME that is bundled with OC4J, or a different one?
Make sure you have oc4jclient.jar in your classpath.
Can you post the section of your script where this call is being made?
-Andrew
On 7/31/06, Angus Rose <[EMAIL PROTECTED]> wrote:
Hi All,
I am creating a scrip
