Hi Chinthaka, I found the solution today: the problems only came about when I dropped a service into axis2. I downloaded the axis2 source from http://svn.apache.org/repos/asf to try and track the problem and discovered that none of that source will build largely because it uses org.apache.axis2.om package structure instead of org.apache.ws.commons.om.
Seemingly, all the service archives that I have dropped in have been using these package names. When I changed one of them to the new(?) ones and rebuilt the aar everything worked without problem. So now I am scratching my head and wondering is this a change from 0.94 or have I picked things up from even earlier versions? Looking back at every experiment I've done with axis2 it seems as if I have the wrong packages. I rebuilt my Eclipse axis2 library after I re-installed Tomcat at your suggestion, so you were right about the classpath problem. It never occurred to me that it was the Eclipse classpath and not the system or Tomcat classpath! Oh well, onwards...! Regards, Ken -----Original Message----- From: Eran Chinthaka [mailto:[EMAIL PROTECTED] Sent: 29 March 2006 17:01 To: [email protected] Subject: Re: [Axis2] 0.95 installation >Anyway, it seems like you have a classpath problem. .... >-- Chinthaka
