We are upgrading from Eclipse 3.1 to 3.2 and TPTP 4.2.0 to 4.2.1. In the
old environment all of our tests executed fine. Now we are experiencing
class loading failures in the Axis library. The odd thing is that the
class that can not be found by name is in the same jar as the class that
is trying to load it, axis.jar. There are two other axis.jar in the
plugins, one is in the axis 1.3 plugin and the other is in one of the
BIRT plugins. In trying to isolate he problem I temporarily removed both
of these; this made no difference. The stacktrace is included below.

Any ideas appreciated.

Thanks,
Joel

!MESSAGE Message: Problem loading class:
org.apache.axis.attachments.AttachmentsImpl
java.lang.NoClassDefFoundError
at
org.apache.axis.handlers.BasicHandler.<clinit>(BasicHandler.java:43)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:242)
at org.apache.axis.utils.ClassUtils$2.run(ClassUtils.java:177)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.axis.utils.ClassUtils.loadClass(ClassUtils.java:1 60)
at org.apache.axis.utils.ClassUtils.forName(ClassUtils.java:100 )
at
org.apache.axis.deployment.wsdd.WSDDTargetedChain.makeNewIns tance(WSDDTargetedChain.java:157)
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewIns tance(WSDDDeployableItem.java:274)
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstan ce(WSDDDeployableItem.java:260)
at
org.apache.axis.deployment.wsdd.WSDDDeployment.getTransport( WSDDDeployment.java:410)
at
org.apache.axis.configuration.FileProvider.getTransport(File Provider.java:257)
at org.apache.axis.AxisEngine.getTransport(AxisEngine.java:332)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:163 )
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at
com.etish.useme.est.webservices.ServerWSSoapBindingStub.auth enticate(ServerWSSoapBindingStub.java:342)
at
com.etish.useme.client.base.core.services.ServerDelegate.val idate(ServerDelegate.java:859)
at
com.etish.useme.client.base.core.services.ServerLiaison.addS erverLocation(ServerLiaison.java:121)
at
com.etish.useme.client.editor.ui.wizards.serverlocation.Serv erLocationWizard.addLocation(ServerLocationWizard.java:90)
at
com.etish.useme.client.editor.ui.wizards.serverlocation.Serv erLocationWizard.performFinish(ServerLocationWizard.java:177 )
at
org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDi alog.java:680)
at
org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDi alog.java:355)
at org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.jav a:660)
at
org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:90)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:952)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:7 09)
at
org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.doClick(BooleanSelectionCommand.java:490)
at
org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.playback(BooleanSelectionCommand.java:294)
at
org.eclipse.tptp.test.auto.gui.internal.commands.MacroComman dShell$4.run(MacroCommandShell.java:1160)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3325)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2971)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:820 )
at org.eclipse.jface.window.Window.open(Window.java:796)
at
org.eclipse.ui.actions.NewWizardAction.run(NewWizardAction.j ava:181)
at
org.eclipse.ui.actions.NewWizardDropDownAction.run(NewWizard DropDownAction.java:174)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:499 )
at
org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:539)
at
org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:488)
at
org.eclipse.jface.action.ActionContributionItem$6.handleEven t(ActionContributionItem.java:441)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:952)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:7 09)
at
org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.doClick(BooleanSelectionCommand.java:490)
at
org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.playback(BooleanSelectionCommand.java:294)
at
org.eclipse.tptp.test.auto.gui.internal.commands.MacroComman dShell$4.run(MacroCommandShell.java:1160)

I guess I should have mentioned that the recording of the this test runs
fine without any exceptions and that I can run our plugin on its own
from the deployed plugins without a problem. The only time we experience
failure is when we are running the test case under AGR.

Joel

Joel Rosi-Schwartz wrote:
> Hi,
>
> We are upgrading from Eclipse 3.1 to 3.2 and TPTP 4.2.0 to 4.2.1. In
> the old environment all of our tests executed fine. Now we are
> experiencing class loading failures in the Axis library. The odd thing
> is that the class that can not be found by name is in the same jar as
> the class that is trying to load it, axis.jar. There are two other
> axis.jar in the plugins, one is in the axis 1.3 plugin and the other
> is in one of the BIRT plugins. In trying to isolate he problem I
> temporarily removed both of these; this made no difference. The
> stacktrace is included below.
>
> Any ideas appreciated.
>
> Thanks,
> Joel
>
> !MESSAGE Message: Problem loading class:
> org.apache.axis.attachments.AttachmentsImpl
> java.lang.NoClassDefFoundError
> at
> org.apache.axis.handlers.BasicHandler.<clinit>(BasicHandler.java:43)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:242)
> at org.apache.axis.utils.ClassUtils$2.run(ClassUtils.java:177)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.apache.axis.utils.ClassUtils.loadClass(ClassUtils.java:1 60)
> at org.apache.axis.utils.ClassUtils.forName(ClassUtils.java:100 )
> at
> org.apache.axis.deployment.wsdd.WSDDTargetedChain.makeNewIns tance(WSDDTargetedChain.java:157)
> at
> org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewIns tance(WSDDDeployableItem.java:274)
> at
> org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstan ce(WSDDDeployableItem.java:260)
> at
> org.apache.axis.deployment.wsdd.WSDDDeployment.getTransport( WSDDDeployment.java:410)
> at
> org.apache.axis.configuration.FileProvider.getTransport(File Provider.java:257)
> at org.apache.axis.AxisEngine.getTransport(AxisEngine.java:332)
> at org.apache.axis.client.AxisClient.invoke(AxisClient.java:163 )
> at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
> at org.apache.axis.client.Call.invoke(Call.java:2767)
> at org.apache.axis.client.Call.invoke(Call.java:2443)
> at org.apache.axis.client.Call.invoke(Call.java:2366)
> at org.apache.axis.client.Call.invoke(Call.java:1812)
> at
> com.etish.useme.est.webservices.ServerWSSoapBindingStub.auth enticate(ServerWSSoapBindingStub.java:342)
> at
> com.etish.useme.client.base.core.services.ServerDelegate.val idate(ServerDelegate.java:859)
> at
> com.etish.useme.client.base.core.services.ServerLiaison.addS erverLocation(ServerLiaison.java:121)
> at
> com.etish.useme.client.editor.ui.wizards.serverlocation.Serv erLocationWizard.addLocation(ServerLocationWizard.java:90)
> at
> com.etish.useme.client.editor.ui.wizards.serverlocation.Serv erLocationWizard.performFinish(ServerLocationWizard.java:177 )
> at
> org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDi alog.java:680)
> at
> org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDi alog.java:355)
> at
> org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.jav a:660)
> at
> org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:90)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:952)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:7 09)
> at
> org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.doClick(BooleanSelectionCommand.java:490)
> at
> org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.playback(BooleanSelectionCommand.java:294)
> at
> org.eclipse.tptp.test.auto.gui.internal.commands.MacroComman dShell$4.run(MacroCommandShell.java:1160)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
> at
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
> at
> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3325)
> at
> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2971)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:820 )
> at org.eclipse.jface.window.Window.open(Window.java:796)
> at
> org.eclipse.ui.actions.NewWizardAction.run(NewWizardAction.j ava:181)
> at
> org.eclipse.ui.actions.NewWizardDropDownAction.run(NewWizard DropDownAction.java:174)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499 )
> at
> org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:539)
> at
> org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:488)
> at
> org.eclipse.jface.action.ActionContributionItem$6.handleEven t(ActionContributionItem.java:441)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:952)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:7 09)
> at
> org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.doClick(BooleanSelectionCommand.java:490)
> at
> org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.playback(BooleanSelectionCommand.java:294)
> at
> org.eclipse.tptp.test.auto.gui.internal.commands.MacroComman dShell$4.run(MacroCommandShell.java:1160)
>
>
>

I had a similar problem a few month ago. What I found out was that the
classpath settings (i.e. the content of environment variable CLASSPATH) that
were in effect while running an AGR test suite confused the eclipse class
loader somehow. After making sure that the CLASSPATH is really empty while
an AGR test executes the problem disappeared. I never had the class loading
problem when acting as a real user. The problem only occurred in context of
AGR execution. Maybe worth a try for you to do the same.

"Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org> wrote in message
news:ejabtq$h5h$1@utils.eclipse.org...
>I guess I should have mentioned that the recording of the this test runs
> fine without any exceptions and that I can run our plugin on its own
> from the deployed plugins without a problem. The only time we experience
> failure is when we are running the test case under AGR.
>
> Joel
>
> Joel Rosi-Schwartz wrote:
>> Hi,
>>
>> We are upgrading from Eclipse 3.1 to 3.2 and TPTP 4.2.0 to 4.2.1. In
>> the old environment all of our tests executed fine. Now we are
>> experiencing class loading failures in the Axis library. The odd thing
>> is that the class that can not be found by name is in the same jar as
>> the class that is trying to load it, axis.jar. There are two other
>> axis.jar in the plugins, one is in the axis 1.3 plugin and the other
>> is in one of the BIRT plugins. In trying to isolate he problem I
>> temporarily removed both of these; this made no difference. The
>> stacktrace is included below.
>>
>> Any ideas appreciated.
>>
>> Thanks,
>> Joel
>>
>> !MESSAGE Message: Problem loading class:
>> org.apache.axis.attachments.AttachmentsImpl
>> java.lang.NoClassDefFoundError
>> at
>> org.apache.axis.handlers.BasicHandler.<clinit>(BasicHandler.java:43)
>> at java.lang.Class.forName0(Native Method)
>> at java.lang.Class.forName(Class.java:242)
>> at org.apache.axis.utils.ClassUtils$2.run(ClassUtils.java:177)
>> at java.security.AccessController.doPrivileged(Native Method)
>> at org.apache.axis.utils.ClassUtils.loadClass(ClassUtils.java:1 60)
>> at org.apache.axis.utils.ClassUtils.forName(ClassUtils.java:100 )
>> at
>>
>> org.apache.axis.deployment.wsdd.WSDDTargetedChain.makeNewIns tance(WSDDTargetedChain.java:157)
>> at
>>
>> org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewIns tance(WSDDDeployableItem.java:274)
>> at
>>
>> org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstan ce(WSDDDeployableItem.java:260)
>> at
>>
>> org.apache.axis.deployment.wsdd.WSDDDeployment.getTransport( WSDDDeployment.java:410)
>> at
>>
>> org.apache.axis.configuration.FileProvider.getTransport(File Provider.java:257)
>> at org.apache.axis.AxisEngine.getTransport(AxisEngine.java:332)
>> at org.apache.axis.client.AxisClient.invoke(AxisClient.java:163 )
>> at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
>> at org.apache.axis.client.Call.invoke(Call.java:2767)
>> at org.apache.axis.client.Call.invoke(Call.java:2443)
>> at org.apache.axis.client.Call.invoke(Call.java:2366)
>> at org.apache.axis.client.Call.invoke(Call.java:1812)
>> at
>>
>> com.etish.useme.est.webservices.ServerWSSoapBindingStub.auth enticate(ServerWSSoapBindingStub.java:342)
>> at
>>
>> com.etish.useme.client.base.core.services.ServerDelegate.val idate(ServerDelegate.java:859)
>> at
>>
>> com.etish.useme.client.base.core.services.ServerLiaison.addS erverLocation(ServerLiaison.java:121)
>> at
>>
>> com.etish.useme.client.editor.ui.wizards.serverlocation.Serv erLocationWizard.addLocation(ServerLocationWizard.java:90)
>> at
>>
>> com.etish.useme.client.editor.ui.wizards.serverlocation.Serv erLocationWizard.performFinish(ServerLocationWizard.java:177 )
>> at
>>
>> org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDi alog.java:680)
>> at
>>
>> org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDi alog.java:355)
>> at
>> org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.jav a:660)
>> at
>>
>> org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:90)
>> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:952)
>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937)
>> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:7 09)
>> at
>>
>> org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.doClick(BooleanSelectionCommand.java:490)
>> at
>>
>> org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.playback(BooleanSelectionCommand.java:294)
>> at
>>
>> org.eclipse.tptp.test.auto.gui.internal.commands.MacroComman dShell$4.run(MacroCommandShell.java:1160)
>> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
>> at
>>
>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>> at
>> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3325)
>> at
>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2971)
>> at org.eclipse.jface.window.Window.runEventLoop(Window.java:820 )
>> at org.eclipse.jface.window.Window.open(Window.java:796)
>> at
>> org.eclipse.ui.actions.NewWizardAction.run(NewWizardAction.j ava:181)
>> at
>>
>> org.eclipse.ui.actions.NewWizardDropDownAction.run(NewWizard DropDownAction.java:174)
>> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499 )
>> at
>>
>> org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:539)
>> at
>>
>> org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:488)
>> at
>>
>> org.eclipse.jface.action.ActionContributionItem$6.handleEven t(ActionContributionItem.java:441)
>> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:952)
>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937)
>> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:7 09)
>> at
>>
>> org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.doClick(BooleanSelectionCommand.java:490)
>> at
>>
>> org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.playback(BooleanSelectionCommand.java:294)
>> at
>>
>> org.eclipse.tptp.test.auto.gui.internal.commands.MacroComman dShell$4.run(MacroCommandShell.java:1160)
>>
>>
>>
>

Thanks once again for assistance, but unfortunately this time it was not
the solution. I do not have the CLASSPATH set in the environment; it is
something that I learned very early on with Java was to always set the
classpath explicitly for every program I am launching IFF it needs one.

Cheers,
Joel

Frank Froehlich wrote:
> I had a similar problem a few month ago. What I found out was that the
> classpath settings (i.e. the content of environment variable CLASSPATH) that
> were in effect while running an AGR test suite confused the eclipse class
> loader somehow. After making sure that the CLASSPATH is really empty while
> an AGR test executes the problem disappeared. I never had the class loading
> problem when acting as a real user. The problem only occurred in context of
> AGR execution. Maybe worth a try for you to do the same.
>
> "Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org> wrote in message
> news:ejabtq$h5h$1@utils.eclipse.org...
>
>> I guess I should have mentioned that the recording of the this test runs
>> fine without any exceptions and that I can run our plugin on its own
>> from the deployed plugins without a problem. The only time we experience
>> failure is when we are running the test case under AGR.
>>
>> Joel
>>
>> Joel Rosi-Schwartz wrote:
>>
>>> Hi,
>>>
>>> We are upgrading from Eclipse 3.1 to 3.2 and TPTP 4.2.0 to 4.2.1. In
>>> the old environment all of our tests executed fine. Now we are
>>> experiencing class loading failures in the Axis library. The odd thing
>>> is that the class that can not be found by name is in the same jar as
>>> the class that is trying to load it, axis.jar. There are two other
>>> axis.jar in the plugins, one is in the axis 1.3 plugin and the other
>>> is in one of the BIRT plugins. In trying to isolate he problem I
>>> temporarily removed both of these; this made no difference. The
>>> stacktrace is included below.
>>>
>>> Any ideas appreciated.
>>>
>>> Thanks,
>>> Joel
>>>
>>> !MESSAGE Message: Problem loading class:
>>> org.apache.axis.attachments.AttachmentsImpl
>>> java.lang.NoClassDefFoundError
>>> at
>>> org.apache.axis.handlers.BasicHandler.<clinit>(BasicHandler.java:43)
>>> at java.lang.Class.forName0(Native Method)
>>> at java.lang.Class.forName(Class.java:242)
>>> at org.apache.axis.utils.ClassUtils$2.run(ClassUtils.java:177)
>>> at java.security.AccessController.doPrivileged(Native Method)
>>> at org.apache.axis.utils.ClassUtils.loadClass(ClassUtils.java:1 60)
>>> at org.apache.axis.utils.ClassUtils.forName(ClassUtils.java:100 )
>>> at
>>>
>>> org.apache.axis.deployment.wsdd.WSDDTargetedChain.makeNewIns tance(WSDDTargetedChain.java:157)
>>> at
>>>
>>> org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewIns tance(WSDDDeployableItem.java:274)
>>> at
>>>
>>> org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstan ce(WSDDDeployableItem.java:260)
>>> at
>>>
>>> org.apache.axis.deployment.wsdd.WSDDDeployment.getTransport( WSDDDeployment.java:410)
>>> at
>>>
>>> org.apache.axis.configuration.FileProvider.getTransport(File Provider.java:257)
>>> at org.apache.axis.AxisEngine.getTransport(AxisEngine.java:332)
>>> at org.apache.axis.client.AxisClient.invoke(AxisClient.java:163 )
>>> at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
>>> at org.apache.axis.client.Call.invoke(Call.java:2767)
>>> at org.apache.axis.client.Call.invoke(Call.java:2443)
>>> at org.apache.axis.client.Call.invoke(Call.java:2366)
>>> at org.apache.axis.client.Call.invoke(Call.java:1812)
>>> at
>>>
>>> com.etish.useme.est.webservices.ServerWSSoapBindingStub.auth enticate(ServerWSSoapBindingStub.java:342)
>>> at
>>>
>>> com.etish.useme.client.base.core.services.ServerDelegate.val idate(ServerDelegate.java:859)
>>> at
>>>
>>> com.etish.useme.client.base.core.services.ServerLiaison.addS erverLocation(ServerLiaison.java:121)
>>> at
>>>
>>> com.etish.useme.client.editor.ui.wizards.serverlocation.Serv erLocationWizard.addLocation(ServerLocationWizard.java:90)
>>> at
>>>
>>> com.etish.useme.client.editor.ui.wizards.serverlocation.Serv erLocationWizard.performFinish(ServerLocationWizard.java:177 )
>>> at
>>>
>>> org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDi alog.java:680)
>>> at
>>>
>>> org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDi alog.java:355)
>>> at
>>> org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.jav a:660)
>>> at
>>>
>>> org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:90)
>>> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:952)
>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937)
>>> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:7 09)
>>> at
>>>
>>> org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.doClick(BooleanSelectionCommand.java:490)
>>> at
>>>
>>> org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.playback(BooleanSelectionCommand.java:294)
>>> at
>>>
>>> org.eclipse.tptp.test.auto.gui.internal.commands.MacroComman dShell$4.run(MacroCommandShell.java:1160)
>>> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
>>> at
>>>
>>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>>> at
>>> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3325)
>>> at
>>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2971)
>>> at org.eclipse.jface.window.Window.runEventLoop(Window.java:820 )
>>> at org.eclipse.jface.window.Window.open(Window.java:796)
>>> at
>>> org.eclipse.ui.actions.NewWizardAction.run(NewWizardAction.j ava:181)
>>> at
>>>
>>> org.eclipse.ui.actions.NewWizardDropDownAction.run(NewWizard DropDownAction.java:174)
>>> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499 )
>>> at
>>>
>>> org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:539)
>>> at
>>>
>>> org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:488)
>>> at
>>>
>>> org.eclipse.jface.action.ActionContributionItem$6.handleEven t(ActionContributionItem.java:441)
>>> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:952)
>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937)
>>> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:7 09)
>>> at
>>>
>>> org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.doClick(BooleanSelectionCommand.java:490)
>>> at
>>>
>>> org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.playback(BooleanSelectionCommand.java:294)
>>> at
>>>
>>> org.eclipse.tptp.test.auto.gui.internal.commands.MacroComman dShell$4.run(MacroCommandShell.java:1160)
>>>
>>>
>>>
>>>
>
>
>

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Helvetica, Arial, sans-serif">Thanks once again for
assistance, but unfortunately this time it was not the solution.&nbsp; I do
not have the CLASSPATH set in the environment; it is something that I
learned very early on with Java was to always set the classpath
explicitly for every program I am launching IFF it needs one. <br>
<br>
Cheers,<br>
Joel<br>
</font><br>
Frank Froehlich wrote:
<blockquote cite="midejbtpr$5d4$1@utils.eclipse.org" type="cite">
<pre wrap="">I had a similar problem a few month ago. What I found out was that the
classpath settings (i.e. the content of environment variable CLASSPATH) that
were in effect while running an AGR test suite confused the eclipse class
loader somehow. After making sure that the CLASSPATH is really empty while
an AGR test executes the problem disappeared. I never had the class loading
problem when acting as a real user. The problem only occurred in context of
AGR execution. Maybe worth a try for you to do the same.

"Joel Rosi-Schwartz" <a class="moz-txt-link-rfc2396E" href="mailto:Joel.Rosi-Schwartz@Etish.org">&lt;Joel.Rosi-Schwartz@Etish.org&gt;</a> wrote in message
<a class="moz-txt-link-freetext" href="news:ejabtq$h5h$1@utils.eclipse.org">news:ejabtq$h5h$1@utils.eclipse.org</a>...
</pre>
<blockquote type="cite">
<pre wrap="">I guess I should have mentioned that the recording of the this test runs
fine without any exceptions and that I can run our plugin on its own
from the deployed plugins without a problem. The only time we experience
failure is when we are running the test case under AGR.

We are upgrading from Eclipse 3.1 to 3.2 and TPTP 4.2.0 to 4.2.1. In
the old environment all of our tests executed fine. Now we are
experiencing class loading failures in the Axis library. The odd thing
is that the class that can not be found by name is in the same jar as
the class that is trying to load it, axis.jar. There are two other
axis.jar in the plugins, one is in the axis 1.3 plugin and the other
is in one of the BIRT plugins. In trying to isolate he problem I
temporarily removed both of these; this made no difference. The
stacktrace is included below.

org.apache.axis.deployment.wsdd.WSDDTargetedChain.makeNewIns tance(WSDDTargetedChain.java:157)
at

org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewIns tance(WSDDDeployableItem.java:274)
at

org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstan ce(WSDDDeployableItem.java:260)
at

org.apache.axis.deployment.wsdd.WSDDDeployment.getTransport( WSDDDeployment.java:410)
at

org.apache.axis.configuration.FileProvider.getTransport(File Provider.java:257)
at org.apache.axis.AxisEngine.getTransport(AxisEngine.java:332)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:163 )
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at

com.etish.useme.est.webservices.ServerWSSoapBindingStub.auth enticate(ServerWSSoapBindingStub.java:342)
at

com.etish.useme.client.base.core.services.ServerDelegate.val idate(ServerDelegate.java:859)
at

com.etish.useme.client.base.core.services.ServerLiaison.addS erverLocation(ServerLiaison.java:121)
at

com.etish.useme.client.editor.ui.wizards.serverlocation.Serv erLocationWizard.addLocation(ServerLocationWizard.java:90)
at

org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDi alog.java:680)
at

org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDi alog.java:355)
at
org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.jav a:660)
at

org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:90)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:952)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:7 09)
at

org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.doClick(BooleanSelectionCommand.java:490)
at

org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.playback(BooleanSelectionCommand.java:294)
at

org.eclipse.tptp.test.auto.gui.internal.commands.MacroComman dShell$4.run(MacroCommandShell.java:1160)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
at

org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
at
org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3325)
at
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2971)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:820 )
at org.eclipse.jface.window.Window.open(Window.java:796)
at
org.eclipse.ui.actions.NewWizardAction.run(NewWizardAction.j ava:181)
at

org.eclipse.ui.actions.NewWizardDropDownAction.run(NewWizard DropDownAction.java:174)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:499 )
at

org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:539)
at

org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:488)
at

org.eclipse.jface.action.ActionContributionItem$6.handleEven t(ActionContributionItem.java:441)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:952)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:7 09)
at

org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.doClick(BooleanSelectionCommand.java:490)
at

org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.playback(BooleanSelectionCommand.java:294)
at

O.k., for me it was envvar CLASSPATH at that time. But there is another
thing: AGR builds up a complex class path for the JVM of the eclipse
instance in which an AGR test is executed. You really shoud check what's in
sysprop "java.class.path" while your test is executed (you can use a VH
method to do so). Due to my bad experience with envvar CLASSPATH, I now
always deliberately add '-classpath
"pathToEclipseRoot\startup.jar;pathToMyVHBinDirectory"' to the vmArguments
of the deployment in use. Only these two class path entries are necessary
for test execution as far as I understand. Anyway, after I switched to this
technique all of my mysterious class loading problems disappeared. Maybe
worth another try for you.

"Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org> wrote in message
news:455A1E7B.6000508@Etish.org...
> Thanks once again for assistance, but unfortunately this time it was not
> the solution. I do not have the CLASSPATH set in the environment; it is
> something that I learned very early on with Java was to always set the
> classpath explicitly for every program I am launching IFF it needs one.
>
> Cheers,
> Joel
>
> Frank Froehlich wrote:
>> I had a similar problem a few month ago. What I found out was that the
>> classpath settings (i.e. the content of environment variable CLASSPATH)
>> that
>> were in effect while running an AGR test suite confused the eclipse class
>> loader somehow. After making sure that the CLASSPATH is really empty
>> while
>> an AGR test executes the problem disappeared. I never had the class
>> loading
>> problem when acting as a real user. The problem only occurred in context
>> of
>> AGR execution. Maybe worth a try for you to do the same.
>>
>> "Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org> wrote in message
>> news:ejabtq$h5h$1@utils.eclipse.org...
>>
>>> I guess I should have mentioned that the recording of the this test runs
>>> fine without any exceptions and that I can run our plugin on its own
>>> from the deployed plugins without a problem. The only time we experience
>>> failure is when we are running the test case under AGR.
>>>
>>> Joel
>>>
>>> Joel Rosi-Schwartz wrote:
>>>
>>>> Hi,
>>>>
>>>> We are upgrading from Eclipse 3.1 to 3.2 and TPTP 4.2.0 to 4.2.1. In
>>>> the old environment all of our tests executed fine. Now we are
>>>> experiencing class loading failures in the Axis library. The odd thing
>>>> is that the class that can not be found by name is in the same jar as
>>>> the class that is trying to load it, axis.jar. There are two other
>>>> axis.jar in the plugins, one is in the axis 1.3 plugin and the other
>>>> is in one of the BIRT plugins. In trying to isolate he problem I
>>>> temporarily removed both of these; this made no difference. The
>>>> stacktrace is included below.
>>>>
>>>> Any ideas appreciated.
>>>>
>>>> Thanks,
>>>> Joel
>>>>
>>>> !MESSAGE Message: Problem loading class:
>>>> org.apache.axis.attachments.AttachmentsImpl
>>>> java.lang.NoClassDefFoundError
>>>> at
>>>>
>>>> org.apache.axis.handlers.BasicHandler.<clinit>(BasicHandler.java:43)
>>>> at java.lang.Class.forName0(Native Method)
>>>> at java.lang.Class.forName(Class.java:242)
>>>> at org.apache.axis.utils.ClassUtils$2.run(ClassUtils.java:177)
>>>> at java.security.AccessController.doPrivileged(Native Method)
>>>> at
>>>> org.apache.axis.utils.ClassUtils.loadClass(ClassUtils.java:1 60)
>>>> at org.apache.axis.utils.ClassUtils.forName(ClassUtils.java:100 )
>>>> at
>>>>
>>>> org.apache.axis.deployment.wsdd.WSDDTargetedChain.makeNewIns tance(WSDDTargetedChain.java:157)
>>>> at
>>>>
>>>> org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewIns tance(WSDDDeployableItem.java:274)
>>>> at
>>>>
>>>> org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstan ce(WSDDDeployableItem.java:260)
>>>> at
>>>>
>>>> org.apache.axis.deployment.wsdd.WSDDDeployment.getTransport( WSDDDeployment.java:410)
>>>> at
>>>>
>>>> org.apache.axis.configuration.FileProvider.getTransport(File Provider.java:257)
>>>> at org.apache.axis.AxisEngine.getTransport(AxisEngine.java:332)
>>>> at org.apache.axis.client.AxisClient.invoke(AxisClient.java:163 )
>>>> at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
>>>> at org.apache.axis.client.Call.invoke(Call.java:2767)
>>>> at org.apache.axis.client.Call.invoke(Call.java:2443)
>>>> at org.apache.axis.client.Call.invoke(Call.java:2366)
>>>> at org.apache.axis.client.Call.invoke(Call.java:1812)
>>>> at
>>>>
>>>> com.etish.useme.est.webservices.ServerWSSoapBindingStub.auth enticate(ServerWSSoapBindingStub.java:342)
>>>> at
>>>>
>>>> com.etish.useme.client.base.core.services.ServerDelegate.val idate(ServerDelegate.java:859)
>>>> at
>>>>
>>>> com.etish.useme.client.base.core.services.ServerLiaison.addS erverLocation(ServerLiaison.java:121)
>>>> at
>>>>
>>>> com.etish.useme.client.editor.ui.wizards.serverlocation.Serv erLocationWizard.addLocation(ServerLocationWizard.java:90)
>>>> at
>>>>
>>>> com.etish.useme.client.editor.ui.wizards.serverlocation.Serv erLocationWizard.performFinish(ServerLocationWizard.java:177 )
>>>> at
>>>>
>>>> org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDi alog.java:680)
>>>> at
>>>>
>>>> org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDi alog.java:355)
>>>> at
>>>> org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.jav a:660)
>>>> at
>>>>
>>>> org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:90)
>>>> at
>>>> org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
>>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
>>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:952)
>>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937)
>>>> at
>>>> org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:7 09)
>>>> at
>>>>
>>>> org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.doClick(BooleanSelectionCommand.java:490)
>>>> at
>>>>
>>>> org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.playback(BooleanSelectionCommand.java:294)
>>>> at
>>>>
>>>> org.eclipse.tptp.test.auto.gui.internal.commands.MacroComman dShell$4.run(MacroCommandShell.java:1160)
>>>> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
>>>> at
>>>>
>>>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>>>> at
>>>> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3325)
>>>> at
>>>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2971)
>>>> at org.eclipse.jface.window.Window.runEventLoop(Window.java:820 )
>>>> at org.eclipse.jface.window.Window.open(Window.java:796)
>>>> at
>>>>
>>>> org.eclipse.ui.actions.NewWizardAction.run(NewWizardAction.j ava:181)
>>>> at
>>>>
>>>> org.eclipse.ui.actions.NewWizardDropDownAction.run(NewWizard DropDownAction.java:174)
>>>> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499 )
>>>> at
>>>>
>>>> org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:539)
>>>> at
>>>>
>>>> org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:488)
>>>> at
>>>>
>>>> org.eclipse.jface.action.ActionContributionItem$6.handleEven t(ActionContributionItem.java:441)
>>>> at
>>>> org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
>>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
>>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:952)
>>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937)
>>>> at
>>>> org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:7 09)
>>>> at
>>>>
>>>> org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.doClick(BooleanSelectionCommand.java:490)
>>>> at
>>>>
>>>> org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.playback(BooleanSelectionCommand.java:294)
>>>> at
>>>>
>>>> org.eclipse.tptp.test.auto.gui.internal.commands.MacroComman dShell$4.run(MacroCommandShell.java:1160)
>>>>
>>>>
>>>>
>>>>
>>
>>
>>
>

I would like to give this a go, but I am at a loss for how to set the
classpath explicitly for the AGR execution when I am starting it via the
Run menu in Eclipse. Are you inferring that I need to set up a test
harness outside of the workspace?

Thanks,
Joel

Frank Froehlich wrote:
> O.k., for me it was envvar CLASSPATH at that time. But there is another
> thing: AGR builds up a complex class path for the JVM of the eclipse
> instance in which an AGR test is executed. You really shoud check what's in
> sysprop "java.class.path" while your test is executed (you can use a VH
> method to do so). Due to my bad experience with envvar CLASSPATH, I now
> always deliberately add '-classpath
> "pathToEclipseRoot\startup.jar;pathToMyVHBinDirectory"' to the vmArguments
> of the deployment in use. Only these two class path entries are necessary
> for test execution as far as I understand. Anyway, after I switched to this
> technique all of my mysterious class loading problems disappeared. Maybe
> worth another try for you.
>
> "Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org> wrote in message
> news:455A1E7B.6000508@Etish.org...
>
>> Thanks once again for assistance, but unfortunately this time it was not
>> the solution. I do not have the CLASSPATH set in the environment; it is
>> something that I learned very early on with Java was to always set the
>> classpath explicitly for every program I am launching IFF it needs one.
>>
>> Cheers,
>> Joel
>>
>> Frank Froehlich wrote:
>>
>>> I had a similar problem a few month ago. What I found out was that the
>>> classpath settings (i.e. the content of environment variable CLASSPATH)
>>> that
>>> were in effect while running an AGR test suite confused the eclipse class
>>> loader somehow. After making sure that the CLASSPATH is really empty
>>> while
>>> an AGR test executes the problem disappeared. I never had the class
>>> loading
>>> problem when acting as a real user. The problem only occurred in context
>>> of
>>> AGR execution. Maybe worth a try for you to do the same.
>>>
>>> "Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org> wrote in message
>>> news:ejabtq$h5h$1@utils.eclipse.org...
>>>
>>>
>>>> I guess I should have mentioned that the recording of the this test runs
>>>> fine without any exceptions and that I can run our plugin on its own
>>>> from the deployed plugins without a problem. The only time we experience
>>>> failure is when we are running the test case under AGR.
>>>>
>>>> Joel
>>>>
>>>> Joel Rosi-Schwartz wrote:
>>>>
>>>>
>>>>> Hi,
>>>>>
>>>>> We are upgrading from Eclipse 3.1 to 3.2 and TPTP 4.2.0 to 4.2.1. In
>>>>> the old environment all of our tests executed fine. Now we are
>>>>> experiencing class loading failures in the Axis library. The odd thing
>>>>> is that the class that can not be found by name is in the same jar as
>>>>> the class that is trying to load it, axis.jar. There are two other
>>>>> axis.jar in the plugins, one is in the axis 1.3 plugin and the other
>>>>> is in one of the BIRT plugins. In trying to isolate he problem I
>>>>> temporarily removed both of these; this made no difference. The
>>>>> stacktrace is included below.
>>>>>
>>>>> Any ideas appreciated.
>>>>>
>>>>> Thanks,
>>>>> Joel
>>>>>
>>>>> !MESSAGE Message: Problem loading class:
>>>>> org.apache.axis.attachments.AttachmentsImpl
>>>>> java.lang.NoClassDefFoundError
>>>>> at
>>>>>
>>>>> org.apache.axis.handlers.BasicHandler.<clinit>(BasicHandler.java:43)
>>>>> at java.lang.Class.forName0(Native Method)
>>>>> at java.lang.Class.forName(Class.java:242)
>>>>> at org.apache.axis.utils.ClassUtils$2.run(ClassUtils.java:177)
>>>>> at java.security.AccessController.doPrivileged(Native Method)
>>>>> at
>>>>> org.apache.axis.utils.ClassUtils.loadClass(ClassUtils.java:1 60)
>>>>> at org.apache.axis.utils.ClassUtils.forName(ClassUtils.java:100 )
>>>>> at
>>>>>
>>>>> org.apache.axis.deployment.wsdd.WSDDTargetedChain.makeNewIns tance(WSDDTargetedChain.java:157)
>>>>> at
>>>>>
>>>>> org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewIns tance(WSDDDeployableItem.java:274)
>>>>> at
>>>>>
>>>>> org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstan ce(WSDDDeployableItem.java:260)
>>>>> at
>>>>>
>>>>> org.apache.axis.deployment.wsdd.WSDDDeployment.getTransport( WSDDDeployment.java:410)
>>>>> at
>>>>>
>>>>> org.apache.axis.configuration.FileProvider.getTransport(File Provider.java:257)
>>>>> at org.apache.axis.AxisEngine.getTransport(AxisEngine.java:332)
>>>>> at org.apache.axis.client.AxisClient.invoke(AxisClient.java:163 )
>>>>> at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
>>>>> at org.apache.axis.client.Call.invoke(Call.java:2767)
>>>>> at org.apache.axis.client.Call.invoke(Call.java:2443)
>>>>> at org.apache.axis.client.Call.invoke(Call.java:2366)
>>>>> at org.apache.axis.client.Call.invoke(Call.java:1812)
>>>>> at
>>>>>
>>>>> com.etish.useme.est.webservices.ServerWSSoapBindingStub.auth enticate(ServerWSSoapBindingStub.java:342)
>>>>> at
>>>>>
>>>>> com.etish.useme.client.base.core.services.ServerDelegate.val idate(ServerDelegate.java:859)
>>>>> at
>>>>>
>>>>> com.etish.useme.client.base.core.services.ServerLiaison.addS erverLocation(ServerLiaison.java:121)
>>>>> at
>>>>>
>>>>> com.etish.useme.client.editor.ui.wizards.serverlocation.Serv erLocationWizard.addLocation(ServerLocationWizard.java:90)
>>>>> at
>>>>>
>>>>> com.etish.useme.client.editor.ui.wizards.serverlocation.Serv erLocationWizard.performFinish(ServerLocationWizard.java:177 )
>>>>> at
>>>>>
>>>>> org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDi alog.java:680)
>>>>> at
>>>>>
>>>>> org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDi alog.java:355)
>>>>> at
>>>>> org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.jav a:660)
>>>>> at
>>>>>
>>>>> org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:90)
>>>>> at
>>>>> org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
>>>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
>>>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:952)
>>>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937)
>>>>> at
>>>>> org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:7 09)
>>>>> at
>>>>>
>>>>> org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.doClick(BooleanSelectionCommand.java:490)
>>>>> at
>>>>>
>>>>> org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.playback(BooleanSelectionCommand.java:294)
>>>>> at
>>>>>
>>>>> org.eclipse.tptp.test.auto.gui.internal.commands.MacroComman dShell$4.run(MacroCommandShell.java:1160)
>>>>> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
>>>>> at
>>>>>
>>>>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>>>>> at
>>>>> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3325)
>>>>> at
>>>>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2971)
>>>>> at org.eclipse.jface.window.Window.runEventLoop(Window.java:820 )
>>>>> at org.eclipse.jface.window.Window.open(Window.java:796)
>>>>> at
>>>>>
>>>>> org.eclipse.ui.actions.NewWizardAction.run(NewWizardAction.j ava:181)
>>>>> at
>>>>>
>>>>> org.eclipse.ui.actions.NewWizardDropDownAction.run(NewWizard DropDownAction.java:174)
>>>>> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499 )
>>>>> at
>>>>>
>>>>> org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:539)
>>>>> at
>>>>>
>>>>> org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:488)
>>>>> at
>>>>>
>>>>> org.eclipse.jface.action.ActionContributionItem$6.handleEven t(ActionContributionItem.java:441)
>>>>> at
>>>>> org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
>>>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
>>>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:952)
>>>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937)
>>>>> at
>>>>> org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:7 09)
>>>>> at
>>>>>
>>>>> org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.doClick(BooleanSelectionCommand.java:490)
>>>>> at
>>>>>
>>>>> org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.playback(BooleanSelectionCommand.java:294)
>>>>> at
>>>>>
>>>>> org.eclipse.tptp.test.auto.gui.internal.commands.MacroComman dShell$4.run(MacroCommandShell.java:1160)
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
>
>
>

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Helvetica, Arial, sans-serif">Could you please enlighten me
on what VH is?<br>
<br>
I would like to give this a go, but I am at a loss for how to set the
classpath explicitly for the AGR execution when I am starting it via
the Run menu in Eclipse. Are you inferring that I need to set up a test
harness outside of the workspace? <br>
<br>
Thanks,<br>
Joel<br>
</font><br>
Frank Froehlich wrote:
<blockquote cite="midejejdh$ker$1@utils.eclipse.org" type="cite">
<pre wrap="">O.k., for me it was envvar CLASSPATH at that time. But there is another
thing: AGR builds up a complex class path for the JVM of the eclipse
instance in which an AGR test is executed. You really shoud check what's in
sysprop "java.class.path" while your test is executed (you can use a VH
method to do so). Due to my bad experience with envvar CLASSPATH, I now
always deliberately add '-classpath
"pathToEclipseRoot\startup.jar;pathToMyVHBinDirectory"' to the vmArguments
of the deployment in use. Only these two class path entries are necessary
for test execution as far as I understand. Anyway, after I switched to this
technique all of my mysterious class loading problems disappeared. Maybe
worth another try for you.

"Joel Rosi-Schwartz" <a class="moz-txt-link-rfc2396E" href="mailto:Joel.Rosi-Schwartz@Etish.org">&lt;Joel.Rosi-Schwartz@Etish.org&gt;</a> wrote in message
<a class="moz-txt-link-freetext" href="news:455A1E7B.6000508@Etish.org">news:455A1E7B.6000508@Etish.org</a>...
</pre>
<blockquote type="cite">
<pre wrap="">Thanks once again for assistance, but unfortunately this time it was not
the solution. I do not have the CLASSPATH set in the environment; it is
something that I learned very early on with Java was to always set the
classpath explicitly for every program I am launching IFF it needs one.

Cheers,
Joel

Frank Froehlich wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I had a similar problem a few month ago. What I found out was that the
classpath settings (i.e. the content of environment variable CLASSPATH)
that
were in effect while running an AGR test suite confused the eclipse class
loader somehow. After making sure that the CLASSPATH is really empty
while
an AGR test executes the problem disappeared. I never had the class
loading
problem when acting as a real user. The problem only occurred in context
of
AGR execution. Maybe worth a try for you to do the same.

</pre>
<blockquote type="cite">
<pre wrap="">I guess I should have mentioned that the recording of the this test runs
fine without any exceptions and that I can run our plugin on its own
from the deployed plugins without a problem. The only time we experience
failure is when we are running the test case under AGR.

Joel

Joel Rosi-Schwartz wrote:

</pre>
<blockquote type="cite">
<pre wrap="">Hi,

We are upgrading from Eclipse 3.1 to 3.2 and TPTP 4.2.0 to 4.2.1. In
the old environment all of our tests executed fine. Now we are
experiencing class loading failures in the Axis library. The odd thing
is that the class that can not be found by name is in the same jar as
the class that is trying to load it, axis.jar. There are two other
axis.jar in the plugins, one is in the axis 1.3 plugin and the other
is in one of the BIRT plugins. In trying to isolate he problem I
temporarily removed both of these; this made no difference. The
stacktrace is included below.

org.apache.axis.handlers.BasicHandler.&lt;clinit&gt; (BasicHandler.java:43)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:242)
at org.apache.axis.utils.ClassUtils$2.run(ClassUtils.java:177)
at java.security.AccessController.doPrivileged(Native Method)
at
org.apache.axis.utils.ClassUtils.loadClass(ClassUtils.java:1 60)
at org.apache.axis.utils.ClassUtils.forName(ClassUtils.java:100 )
at

org.apache.axis.deployment.wsdd.WSDDTargetedChain.makeNewIns tance(WSDDTargetedChain.java:157)
at

org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewIns tance(WSDDDeployableItem.java:274)
at

org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstan ce(WSDDDeployableItem.java:260)
at

org.apache.axis.deployment.wsdd.WSDDDeployment.getTransport( WSDDDeployment.java:410)
at

org.apache.axis.configuration.FileProvider.getTransport(File Provider.java:257)
at org.apache.axis.AxisEngine.getTransport(AxisEngine.java:332)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:163 )
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at

com.etish.useme.est.webservices.ServerWSSoapBindingStub.auth enticate(ServerWSSoapBindingStub.java:342)
at

com.etish.useme.client.base.core.services.ServerDelegate.val idate(ServerDelegate.java:859)
at

com.etish.useme.client.base.core.services.ServerLiaison.addS erverLocation(ServerLiaison.java:121)
at

com.etish.useme.client.editor.ui.wizards.serverlocation.Serv erLocationWizard.addLocation(ServerLocationWizard.java:90)
at

org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDi alog.java:680)
at

org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDi alog.java:355)
at
org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.jav a:660)
at

org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:90)
at
org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:952)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937)
at
org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:7 09)
at

org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.doClick(BooleanSelectionCommand.java:490)
at

org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.playback(BooleanSelectionCommand.java:294)
at

org.eclipse.tptp.test.auto.gui.internal.commands.MacroComman dShell$4.run(MacroCommandShell.java:1160)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
at

org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
at
org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3325)
at
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2971)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:820 )
at org.eclipse.jface.window.Window.open(Window.java:796)
at

org.eclipse.ui.actions.NewWizardAction.run(NewWizardAction.j ava:181)
at

org.eclipse.ui.actions.NewWizardDropDownAction.run(NewWizard DropDownAction.java:174)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:499 )
at

org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:539)
at

org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:488)
at

org.eclipse.jface.action.ActionContributionItem$6.handleEven t(ActionContributionItem.java:441)
at
org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:952)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937)
at
org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:7 09)
at

org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.doClick(BooleanSelectionCommand.java:490)
at

org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.playback(BooleanSelectionCommand.java:294)
at

1. VH = verification hook
2. As far as I know you are using v4.2.1 (right?). Depending on this and
additionally depending on the assumption that you are using local_deployment
when using "Run", the only thing you would have to do is filling the field
labeled with "JVM Arguments:" on the Overview page of your test suite with
for example '-classpath
" absolutePathOfEclipseRoot\startup.jar;absolutePathOfMyVHBinD irectory " -Xms128m
-Xmx256m'.

Just to be very clear, here is the content of the field mentioned above of
one of my test suites:
-classpath
" D:\Temp\ffr\ecl-3.2.1\eclipse\startup.jar;D:\Temp\ffr\ecl-3. 2.1\workspaces\xxx-tests\XCIV22AutoGUITestContainer\bin "
-Xms128m -Xmx256m

If you are not using local_deployment, things are different. You need to set
variable vmArguments in your deployment then. The value for this variable
would be the same as you would enter into the input field mentioned above. I
didn't try out this way for v4.2.1 by now. With v4.1.0.1 it works as
described.

"Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org> wrote in message
news:ejg1bq$oqc$1@utils.eclipse.org...
> Could you please enlighten me on what VH is?
>
> I would like to give this a go, but I am at a loss for how to set the
> classpath explicitly for the AGR execution when I am starting it via the
> Run menu in Eclipse. Are you inferring that I need to set up a test
> harness outside of the workspace?
>
> Thanks,
> Joel
>
> Frank Froehlich wrote:
>> O.k., for me it was envvar CLASSPATH at that time. But there is another
>> thing: AGR builds up a complex class path for the JVM of the eclipse
>> instance in which an AGR test is executed. You really shoud check what's
>> in
>> sysprop "java.class.path" while your test is executed (you can use a VH
>> method to do so). Due to my bad experience with envvar CLASSPATH, I now
>> always deliberately add '-classpath
>> "pathToEclipseRoot\startup.jar;pathToMyVHBinDirectory"' to the
>> vmArguments
>> of the deployment in use. Only these two class path entries are necessary
>> for test execution as far as I understand. Anyway, after I switched to
>> this
>> technique all of my mysterious class loading problems disappeared. Maybe
>> worth another try for you.
>>
>> "Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org> wrote in message
>> news:455A1E7B.6000508@Etish.org...
>>
>>> Thanks once again for assistance, but unfortunately this time it was not
>>> the solution. I do not have the CLASSPATH set in the environment; it is
>>> something that I learned very early on with Java was to always set the
>>> classpath explicitly for every program I am launching IFF it needs one.
>>>
>>> Cheers,
>>> Joel
>>>
>>> Frank Froehlich wrote:
>>>
>>>> I had a similar problem a few month ago. What I found out was that the
>>>> classpath settings (i.e. the content of environment variable CLASSPATH)
>>>> that
>>>> were in effect while running an AGR test suite confused the eclipse
>>>> class
>>>> loader somehow. After making sure that the CLASSPATH is really empty
>>>> while
>>>> an AGR test executes the problem disappeared. I never had the class
>>>> loading
>>>> problem when acting as a real user. The problem only occurred in
>>>> context
>>>> of
>>>> AGR execution. Maybe worth a try for you to do the same.
>>>>
>>>> "Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org> wrote in message
>>>> news:ejabtq$h5h$1@utils.eclipse.org...
>>>>
>>>>
>>>>> I guess I should have mentioned that the recording of the this test
>>>>> runs
>>>>> fine without any exceptions and that I can run our plugin on its own
>>>>> from the deployed plugins without a problem. The only time we
>>>>> experience
>>>>> failure is when we are running the test case under AGR.
>>>>>
>>>>> Joel
>>>>>
>>>>> Joel Rosi-Schwartz wrote:
>>>>>
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> We are upgrading from Eclipse 3.1 to 3.2 and TPTP 4.2.0 to 4.2.1. In
>>>>>> the old environment all of our tests executed fine. Now we are
>>>>>> experiencing class loading failures in the Axis library. The odd
>>>>>> thing
>>>>>> is that the class that can not be found by name is in the same jar as
>>>>>> the class that is trying to load it, axis.jar. There are two other
>>>>>> axis.jar in the plugins, one is in the axis 1.3 plugin and the other
>>>>>> is in one of the BIRT plugins. In trying to isolate he problem I
>>>>>> temporarily removed both of these; this made no difference. The
>>>>>> stacktrace is included below.
>>>>>>
>>>>>> Any ideas appreciated.
>>>>>>
>>>>>> Thanks,
>>>>>> Joel
>>>>>>
>>>>>> !MESSAGE Message: Problem loading class:
>>>>>> org.apache.axis.attachments.AttachmentsImpl
>>>>>> java.lang.NoClassDefFoundError
>>>>>> at
>>>>>>
>>>>>> org.apache.axis.handlers.BasicHandler.<clinit>(BasicHandler.java:43)
>>>>>> at java.lang.Class.forName0(Native Method)
>>>>>> at java.lang.Class.forName(Class.java:242)
>>>>>> at org.apache.axis.utils.ClassUtils$2.run(ClassUtils.java:177)
>>>>>> at java.security.AccessController.doPrivileged(Native Method)
>>>>>> at
>>>>>> org.apache.axis.utils.ClassUtils.loadClass(ClassUtils.java:1 60)
>>>>>> at
>>>>>> org.apache.axis.utils.ClassUtils.forName(ClassUtils.java:100 )
>>>>>> at
>>>>>>
>>>>>> org.apache.axis.deployment.wsdd.WSDDTargetedChain.makeNewIns tance(WSDDTargetedChain.java:157)
>>>>>> at
>>>>>>
>>>>>> org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewIns tance(WSDDDeployableItem.java:274)
>>>>>> at
>>>>>>
>>>>>> org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstan ce(WSDDDeployableItem.java:260)
>>>>>> at
>>>>>>
>>>>>> org.apache.axis.deployment.wsdd.WSDDDeployment.getTransport( WSDDDeployment.java:410)
>>>>>> at
>>>>>>
>>>>>> org.apache.axis.configuration.FileProvider.getTransport(File Provider.java:257)
>>>>>> at org.apache.axis.AxisEngine.getTransport(AxisEngine.java:332)
>>>>>> at
>>>>>> org.apache.axis.client.AxisClient.invoke(AxisClient.java:163 )
>>>>>> at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
>>>>>> at org.apache.axis.client.Call.invoke(Call.java:2767)
>>>>>> at org.apache.axis.client.Call.invoke(Call.java:2443)
>>>>>> at org.apache.axis.client.Call.invoke(Call.java:2366)
>>>>>> at org.apache.axis.client.Call.invoke(Call.java:1812)
>>>>>> at
>>>>>>
>>>>>> com.etish.useme.est.webservices.ServerWSSoapBindingStub.auth enticate(ServerWSSoapBindingStub.java:342)
>>>>>> at
>>>>>>
>>>>>> com.etish.useme.client.base.core.services.ServerDelegate.val idate(ServerDelegate.java:859)
>>>>>> at
>>>>>>
>>>>>> com.etish.useme.client.base.core.services.ServerLiaison.addS erverLocation(ServerLiaison.java:121)
>>>>>> at
>>>>>>
>>>>>> com.etish.useme.client.editor.ui.wizards.serverlocation.Serv erLocationWizard.addLocation(ServerLocationWizard.java:90)
>>>>>> at
>>>>>>
>>>>>> com.etish.useme.client.editor.ui.wizards.serverlocation.Serv erLocationWizard.performFinish(ServerLocationWizard.java:177 )
>>>>>> at
>>>>>>
>>>>>> org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDi alog.java:680)
>>>>>> at
>>>>>>
>>>>>> org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDi alog.java:355)
>>>>>> at
>>>>>>
>>>>>> org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.jav a:660)
>>>>>> at
>>>>>>
>>>>>> org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:90)
>>>>>> at
>>>>>> org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
>>>>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
>>>>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:952)
>>>>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937)
>>>>>> at
>>>>>> org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:7 09)
>>>>>> at
>>>>>>
>>>>>> org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.doClick(BooleanSelectionCommand.java:490)
>>>>>> at
>>>>>>
>>>>>> org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.playback(BooleanSelectionCommand.java:294)
>>>>>> at
>>>>>>
>>>>>> org.eclipse.tptp.test.auto.gui.internal.commands.MacroComman dShell$4.run(MacroCommandShell.java:1160)
>>>>>> at
>>>>>> org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
>>>>>> at
>>>>>>
>>>>>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>>>>>> at
>>>>>>
>>>>>> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3325)
>>>>>> at
>>>>>>
>>>>>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2971)
>>>>>> at
>>>>>> org.eclipse.jface.window.Window.runEventLoop(Window.java:820 )
>>>>>> at org.eclipse.jface.window.Window.open(Window.java:796)
>>>>>> at
>>>>>>
>>>>>> org.eclipse.ui.actions.NewWizardAction.run(NewWizardAction.j ava:181)
>>>>>> at
>>>>>>
>>>>>> org.eclipse.ui.actions.NewWizardDropDownAction.run(NewWizard DropDownAction.java:174)
>>>>>> at
>>>>>> org.eclipse.jface.action.Action.runWithEvent(Action.java:499 )
>>>>>> at
>>>>>>
>>>>>> org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:539)
>>>>>> at
>>>>>>
>>>>>> org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:488)
>>>>>> at
>>>>>>
>>>>>> org.eclipse.jface.action.ActionContributionItem$6.handleEven t(ActionContributionItem.java:441)
>>>>>> at
>>>>>> org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
>>>>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
>>>>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:952)
>>>>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937)
>>>>>> at
>>>>>> org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:7 09)
>>>>>> at
>>>>>>
>>>>>> org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.doClick(BooleanSelectionCommand.java:490)
>>>>>> at
>>>>>>
>>>>>> org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.playback(BooleanSelectionCommand.java:294)
>>>>>> at
>>>>>>
>>>>>> org.eclipse.tptp.test.auto.gui.internal.commands.MacroComman dShell$4.run(MacroCommandShell.java:1160)
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>
>>
>>
>

Is Axis.jar in a plug-in that you have declared a dependency on in your =
test plug-in (via the manifest file)?
Or is Axis.jar a standalone jar file that you've added as part of the =
build path (via the properties dialog of the project)?

At what point does the class not found error occur (during the execution =
of a verification hook or while executing macro commands)?
If you have a context defined under the overview page of the test suite, =
then you'll need to make sure that the context contains the correct =
plug-in.

We are upgrading from Eclipse 3.1 to 3.2 and TPTP 4.2.0 to 4.2.1. In =
the old environment all of our tests executed fine. Now we are =
experiencing class loading failures in the Axis library. The odd thing =
is that the class that can not be found by name is in the same jar as =
the class that is trying to load it, axis.jar. There are two other =
axis.jar in the plugins, one is in the axis 1.3 plugin and the other is =
in one of the BIRT plugins. In trying to isolate he problem I =
temporarily removed both of these; this made no difference. The =
stacktrace is included below.

As you predicted, the classpath variable was not empty at AGR execution
time and setting it in the JVM Arguments for the test suite worked like
a charm.

Thank you very much.

Tschuess,
Barbara

Frank Froehlich wrote:
> 1. VH = verification hook
> 2. As far as I know you are using v4.2.1 (right?). Depending on this and
> additionally depending on the assumption that you are using local_deployment
> when using "Run", the only thing you would have to do is filling the field
> labeled with "JVM Arguments:" on the Overview page of your test suite with
> for example '-classpath
> " absolutePathOfEclipseRoot\startup.jar;absolutePathOfMyVHBinD irectory " -Xms128m
> -Xmx256m'.
>
> Just to be very clear, here is the content of the field mentioned above of
> one of my test suites:
> -classpath
> " D:\Temp\ffr\ecl-3.2.1\eclipse\startup.jar;D:\Temp\ffr\ecl-3. 2.1\workspaces\xxx-tests\XCIV22AutoGUITestContainer\bin "
> -Xms128m -Xmx256m
>
> If you are not using local_deployment, things are different. You need to set
> variable vmArguments in your deployment then. The value for this variable
> would be the same as you would enter into the input field mentioned above. I
> didn't try out this way for v4.2.1 by now. With v4.1.0.1 it works as
> described.
>

As you may have seen already Frank's recommendation in this thread has
resolved the issue. :-) If you would still would find it useful to have
your questions below answered, please let me know I will be happy to
reply to the specifics.

What I wonder now, though, is whether or not this behavior is a bug that
should be reported. Why is this not a widely observed experience of
TPTP/AGR users? Are we doing something aberrant or have we simply
managed to uncover an infrequently exercised issue? Your opinion would
be appreciated.

Please let us know what we can do assist to resolve this in general.

Thanks,
Joel

Ali Mehregani wrote:
> Hi Joel,
>
> Is Axis.jar in a plug-in that you have declared a dependency on in
> your test plug-in (via the manifest file)?
> Or is Axis.jar a standalone jar file that you've added as part of the
> build path (via the properties dialog of the project)?
>
> At what point does the class not found error occur (during the
> execution of a verification hook or while executing macro commands)?
> If you have a context defined under the overview page of the test
> suite, then you'll need to make sure that the context contains the
> correct plug-in.
>
> Thanks,
> Ali Mehregani
>
> "Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org
> <mailto:Joel.Rosi-Schwartz@Etish.org>> wrote in message
> news:ejab22$2qc$1@utils.eclipse.org...
> Hi,
>
> We are upgrading from Eclipse 3.1 to 3.2 and TPTP 4.2.0 to 4.2.1.
> In the old environment all of our tests executed fine. Now we are
> experiencing class loading failures in the Axis library. The odd
> thing is that the class that can not be found by name is in the
> same jar as the class that is trying to load it, axis.jar. There
> are two other axis.jar in the plugins, one is in the axis 1.3
> plugin and the other is in one of the BIRT plugins. In trying to
> isolate he problem I temporarily removed both of these; this made
> no difference. The stacktrace is included below.
>
> Any ideas appreciated.
>
> Thanks,
> Joel
>
> !MESSAGE Message: Problem loading class:
> org.apache.axis.attachments.AttachmentsImpl
> java.lang.NoClassDefFoundError
> at
> org.apache.axis.handlers.BasicHandler.<clinit>(BasicHandler.java:43)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:242)
> at org.apache.axis.utils.ClassUtils$2.run(ClassUtils.java:177)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.apache.axis.utils.ClassUtils.loadClass(ClassUtils.java:1 60)
> at org.apache.axis.utils.ClassUtils.forName(ClassUtils.java:100 )
> at
> org.apache.axis.deployment.wsdd.WSDDTargetedChain.makeNewIns tance(WSDDTargetedChain.java:157)
> at
> org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewIns tance(WSDDDeployableItem.java:274)
> at
> org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstan ce(WSDDDeployableItem.java:260)
> at
> org.apache.axis.deployment.wsdd.WSDDDeployment.getTransport( WSDDDeployment.java:410)
> at
> org.apache.axis.configuration.FileProvider.getTransport(File Provider.java:257)
> at org.apache.axis.AxisEngine.getTransport(AxisEngine.java:332)
> at org.apache.axis.client.AxisClient.invoke(AxisClient.java:163 )
> at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
> at org.apache.axis.client.Call.invoke(Call.java:2767)
> at org.apache.axis.client.Call.invoke(Call.java:2443)
> at org.apache.axis.client.Call.invoke(Call.java:2366)
> at org.apache.axis.client.Call.invoke(Call.java:1812)
> at
> com.etish.useme.est.webservices.ServerWSSoapBindingStub.auth enticate(ServerWSSoapBindingStub.java:342)
> at
> com.etish.useme.client.base.core.services.ServerDelegate.val idate(ServerDelegate.java:859)
> at
> com.etish.useme.client.base.core.services.ServerLiaison.addS erverLocation(ServerLiaison.java:121)
> at
> com.etish.useme.client.editor.ui.wizards.serverlocation.Serv erLocationWizard.addLocation(ServerLocationWizard.java:90)
> at
> com.etish.useme.client.editor.ui.wizards.serverlocation.Serv erLocationWizard.performFinish(ServerLocationWizard.java:177 )
> at
> org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDi alog.java:680)
> at
> org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDi alog.java:355)
> at
> org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.jav a:660)
> at
> org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:90)
> at
> org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:952)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937)
> at
> org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:7 09)
> at
> org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.doClick(BooleanSelectionCommand.java:490)
> at
> org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.playback(BooleanSelectionCommand.java:294)
> at
> org.eclipse.tptp.test.auto.gui.internal.commands.MacroComman dShell$4.run(MacroCommandShell.java:1160)
> at
> org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
> at
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
> at
> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3325)
> at
> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2971)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:820 )
> at org.eclipse.jface.window.Window.open(Window.java:796)
> at
> org.eclipse.ui.actions.NewWizardAction.run(NewWizardAction.j ava:181)
> at
> org.eclipse.ui.actions.NewWizardDropDownAction.run(NewWizard DropDownAction.java:174)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499 )
> at
> org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:539)
> at
> org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:488)
> at
> org.eclipse.jface.action.ActionContributionItem$6.handleEven t(ActionContributionItem.java:441)
> at
> org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:952)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937)
> at
> org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:7 09)
> at
> org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.doClick(BooleanSelectionCommand.java:490)
> at
> org.eclipse.tptp.test.auto.gui.internal.commands.BooleanSele ctionCommand.playback(BooleanSelectionCommand.java:294)
> at
> org.eclipse.tptp.test.auto.gui.internal.commands.MacroComman dShell$4.run(MacroCommandShell.java:1160)
>
>
>

I'm also interested to know why a test suite that runs fine in a =
TPTP4.1.0 environment is failing under TPTP4.2.0. I wonder if there is =
anything specific in your project structure that is causing this =
behavior. If you can provide me with a set of steps for reproducing =
this problem, then please open a defect. =20

If your test plug-in contains non-confidential material, then please =
attach it as part of the defect.

As you may have seen already Frank's recommendation in this thread has =
resolved the issue. :-) If you would still would find it useful to have =
your questions below answered, please let me know I will be happy to =
reply to the specifics.

What I wonder now, though, is whether or not this behavior is a bug =
that should be reported. Why is this not a widely observed experience of =
TPTP/AGR users? Are we doing something aberrant or have we simply =
managed to uncover an infrequently exercised issue? Your opinion would =
be appreciated.

Please let us know what we can do assist to resolve this in general.

Thanks,
Joel =20

Ali Mehregani wrote:=20
Hi Joel,

Is Axis.jar in a plug-in that you have declared a dependency on in =
your test plug-in (via the manifest file)?
Or is Axis.jar a standalone jar file that you've added as part of =
the build path (via the properties dialog of the project)?

At what point does the class not found error occur (during the =
execution of a verification hook or while executing macro commands)?
If you have a context defined under the overview page of the test =
suite, then you'll need to make sure that the context contains the =
correct plug-in.

We are upgrading from Eclipse 3.1 to 3.2 and TPTP 4.2.0 to 4.2.1. =
In the old environment all of our tests executed fine. Now we are =
experiencing class loading failures in the Axis library. The odd thing =
is that the class that can not be found by name is in the same jar as =
the class that is trying to load it, axis.jar. There are two other =
axis.jar in the plugins, one is in the axis 1.3 plugin and the other is =
in one of the BIRT plugins. In trying to isolate he problem I =
temporarily removed both of these; this made no difference. The =
stacktrace is included below.