Hi Chinthaka,
Now that I understand the problem I just need to refactor my services.
However, I am a bit confused when you say that you refactored om *after*
0.95. Does this mean the refactoring is now *in* 0.95, or does it mean it
will be in 0.96?
The Eclipse Axis code generator (which I downloaded from the 0.94 release)
produces a skeleton for me which has methods like:
public org.apache.axis2.om.OMElement getPage(
org.apache.axis2.om.OMElement param0) {
//Todo fill this with the necessary business logic
return null;
}
However, the 0.95 jars that I am using in my build path have
org.apache.ws.common.om.OMElement. I am pointing at
%TOMCAT_HOME%/webapps/axis2/WEB-INF/lib/axiom-api-0.95.jar which is the
directory that the 'magic' axis2.war created.
Yet the svn repository (which I would have thought would have the latest
source) is the same as the Eclipse generator signatures.
Which is the old package name and which is the new?
Regards,
Ken
-----Original Message-----
From: Eran Chinthaka [mailto:[EMAIL PROTECTED]
Sent: 30 March 2006 12:38
To: [email protected]
Subject: Re: [Axis2] 0.95 installation
Hi Ken,
Soon after Axis2 0.95 release I did a package name refactoring in OM. So
you will not able to use the latest om with Axis2 0.95.
But if you are only using the jars came with the release, you wouldn't
have got this issue.
Are you saying that you are getting errors even when using the jars came
in Axis2 0.95 ? If yes, let us reproduce the problem and we'll see what
we can do.
-- Chinthaka
