• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Odd exception with Axis 1.4 and ant taskdef

David Brossard
Ranch Hand
Posts: 109
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,

I've suddenly had a new exception pop up in my world of java apps exposed as Axis 1.x web services (I currently use Axis 1.4).

It's suddenly appeared w/out my remembering changing anything to my environment - obviously this must be a fallacy.

When I use Axis ant tasks (e.g. java2wsdl...) I have to define those tasks. And to achieve this I add the following line to my init task in my ant build file:

<taskdef resource="axis-tasks.properties" classpathref="classpath" />

My classpath contains the following:

<path id="classpath">
<pathelement location="${bin.dir}"/>
<fileset dir="${axis-1.4.lib}" includes="*.jar"/>
<fileset dir="${junit.lib}" includes="*.jar"/>
<fileset dir="${generics.dist.dir}" includes="*.jar"/>
<fileset dir="${etc.dir}" includes="data/*"/>

And my axis libs are nice and fresh. Yet I get the following exception when I run the init, compile, or any of the other related tasks. The irony is that it still seems to work - my wsdl is properly generated and so are the stubs / skeleton.

So in fact, I get this horrendous stacktrace which pollutes my console and that's that - the rest works fine. Any ideas what this may be due to?

  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic