I have had problems with Axis2 on WAS v5r1, specifically with the
QName class.
I found that I had to remove the following JARs from the websphere
appserver lib directory:
qname.jar
webservices.jar
In fact, I just renamed the JARs in case I want to put them back
later (to *.jar_).
These JARs (well, the directory anyway) is on ws.ext.dirs: they are
loaded before/in-preference-to the JARs in the axis2.war, which leads
to runtime issues because the classes they contain have changed since
the release of WAS v5r1.
With the JARs renamed, I can use Axis2 to host web services on WAS
v5r1 ...
Aaron.
On 3-Apr-07, at 11:16 AM, Moorthy GT wrote:
Angel:
Thanks for your reply. Is axis 2 compatible with Websphere 5.1?
Can you give me the command to generate WSDD from WSDl using
WSDL2JAVA tool?
Thanks,
Moorthy
Hi,
Do you really have a requirement to use Axis1 ? You'd better use Axis2
IMO. Otherwise it's perfectly fine to generate service descriptors
from a WSDL file, using the wsdl2java tool.
Regards,
Angel
--
View this message in context: http://www.nabble.com/Migrating-.net-
web-service-to-axis-HELP-tf3514920.html#a9814694
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_________________________________
Aaron Aston | Twisted Pair | 905.852.0950
