Forum Discussion

Thierry_Roussel's avatar
Thierry_Roussel
New Contributor
16 years ago

NullPointerExceptin when running Axis1/Axis2 command line tool

Hello,

I keep getting a NullPointerException when running axis1 (and axis2) through the command line tool (and through maven plug-in). If I run it through saopUI, everything runs fine.
When running wsi (conformance report generation) through the cimmand line, everything run fine.

Issued command :
c:\>toolrunner.bat -iFindGetSOAPBinding -taxis1 -sC:\temp\soapui-settings.xml  c:\temp\FindGet-soapui-project.xml
soapUI 2.5.1 Tool Runner
Configuring log4j from [C:\Program Files\eviware\soapUI-2.5.1\bin\soapui-log4j.xml]
09:28:05,553 INFO  [DefaultSoapUICore] initialized soapui-settings from [C:\Docume~1\OTRE7276\soapui-settings.xml]
09:28:07,021 INFO  [WsdlProject] Loaded project from [file:/c:/temp/FindGet-soapui-project.xml]
09:28:07,740 INFO  [SoapUIToolRunner] Running tools [axis1] for interface [FindGetSOAPBinding] in project [FindGet]
09:28:07,756 INFO  [SoapUIToolRunner] Running tool [axis1] for Interface [FindGetSOAPBinding]
09:28:07,756 ERROR [SoapUI] An error occured [java.lang.NullPointerException], see error log for details
java.lang.NullPointerException
        at com.eviware.x.form.XFormFactory.createDialogBuilder(XFormFactory.java:19)
        at com.eviware.soapui.impl.wsdl.actions.iface.tools.axis1.Axis1XWSDL2JavaAction.buildDialog(Axis1XWSDL2JavaAction.java:82)
        at com.eviware.soapui.impl.wsdl.actions.iface.tools.axis1.Axis1XWSDL2JavaAction.buildDialog(Axis1XWSDL2JavaAction.java:40)
        at com.eviware.soapui.impl.wsdl.actions.iface.tools.support.AbstractToolsAction.perform(AbstractToolsAction.java:113)
        at com.eviware.soapui.tools.SoapUIToolRunner.runTool(SoapUIToolRunner.java:208)
        at com.eviware.soapui.tools.SoapUIToolRunner.runRunner(SoapUIToolRunner.java:120)
        at com.eviware.soapui.tools.AbstractSoapUIRunner.run(AbstractSoapUIRunner.java:127)
        at com.eviware.soapui.tools.AbstractSoapUIRunner.runFromCommandLine(AbstractSoapUIRunner.java:72)
        at com.eviware.soapui.tools.SoapUIToolRunner.main(SoapUIToolRunner.java:71)
09:28:07,771 INFO  [SoapUIToolRunner] time taken: 28ms

The same error occurs if I use the soapUI/Maven2 plugin (Enabling debug doesn't give more information) :
[INFO] [soapui:tool]
soapUI 2.5.1 Maven2 Tool Runner
09:49:14,470 WARN  [DefaultSoapUICore] Missing folder [E:\workspace\soapUITest\.\ext] for external libraries
09:49:15,173 INFO  [DefaultSoapUICore] initialized soapui-settings from [C:\temp\soapui-settings.xml]
09:49:16,689 INFO  [WsdlProject] Loaded project from [file:/c:/temp/FindGet-soapui-project.xml]
09:49:17,501 INFO  [SoapUIToolRunner] Running tools [axis1] for interface [FindGetSOAPBinding] in project [FindGet]
09:49:17,517 INFO  [SoapUIToolRunner] Running tool [axis1] for Interface [FindGetSOAPBinding]
09:49:17,517 ERROR [SoapUI] An error occured [java.lang.NullPointerException], see error log for details
java.lang.NullPointerException
at com.eviware.x.form.XFormFactory.createDialogBuilder(XFormFactory.java:19)
at com.eviware.soapui.impl.wsdl.actions.iface.tools.axis1.Axis1XWSDL2JavaAction.buildDialog(Axis1XWSDL2JavaAction.java:82)
at com.eviware.soapui.impl.wsdl.actions.iface.tools.axis1.Axis1XWSDL2JavaAction.buildDialog(Axis1XWSDL2JavaAction.java:40)
at com.eviware.soapui.impl.wsdl.actions.iface.tools.support.AbstractToolsAction.perform(AbstractToolsAction.java:113)
at com.eviware.soapui.tools.SoapUIToolRunner.runTool(SoapUIToolRunner.java:208)
at com.eviware.soapui.tools.SoapUIToolRunner.runRunner(SoapUIToolRunner.java:120)
at com.eviware.soapui.tools.AbstractSoapUIRunner.run(AbstractSoapUIRunner.java:127)
at com.eviware.soapui.maven2.ToolMojo.execute(ToolMojo.java:65)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:579)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149)
at org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
at org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904)
at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:52)
09:49:17,548 INFO  [SoapUIToolRunner] time taken: 52ms
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 18 seconds
[INFO] Finished at: Thu Apr 02 09:49:17 CEST 2009
[INFO] Final Memory: 4M/10M
[INFO] ------------------------------------------------------------------------

Any suggestions?  Thanks!

3 Replies

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    Hi Thierry,


    Thank you for posting! You actually stumbled on a bug. You can track it and get informed when it's solved.


    Cheers!
    /Nenad Nikolic a.k.a. Shonzilla
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    Hi Thierry,


    This bug #2737635 has been fixed. Please verify it and close the bug.
    The fix will appear in the first nightly build available here.


    Cheers!
    /Nenad Nikolic a.k.a. Shonzilla
  • Hi Shonzilla!

    It runs OK with toolrunner, but I cannot test through maven since the soapui 2.5.2 plug-in does not yet exist in the maven2 repository.
    I tested on the 2009-04-22 nightly build.

    Anyway, you can close the bug.

    Thanks for the quick fix.

    Thierry