business of Sender. This transmission is of a confidential nature
and Sender does not endorse distribution to any party other than intended
recipient. Sender does not necessarily endorse content contained within this
transmission.
Subject: RE: CXF Mtom service and Axis2 Axiom client (FIX)Date: Mon
| Hamilton
From: Martin Gainty [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 02, 2000 5:13 PM
To: axis-user@ws.apache.org
Subject: Re: CXF Mtom service and Axis2 Axiom client (FIX)
not sure what you mean by *painful*
if you have a better algorithm which better
hould update the AXIS FAQ..
Thanks Mike
Martin
- Original Message -
From: Hu, Mary - ITG
To: axis-user@ws.apache.org
Sent: Friday, November 02, 2007 11:40 AM
Subject: RE: CXF Mtom service and Axis2 Axiom client (FIX)
I've just gone through those conflict jars issues. It
:[EMAIL PROTECTED]
Sent: Friday, November 02, 2007 1:07 PM
To: axis-user@ws.apache.org
Subject: RE: CXF Mtom service and Axis2 Axiom client (FIX)
Hey Mike,
what is the compelling reason that impelled you to move to CXF
(presumably from Axis2, or XFire)?
-jeff
: CXF Mtom service and Axis2 Axiom client (FIX)
FYI:
I finally got it working. turns out it is a classpath issue.
I have CXF and Axis2 in the same eclipse project and Java WS
clients written with both frameworks.
I moved the Axis2
I've just gone through those conflict jars issues. It was really painful
in XML world.
_
From: Barlotta, Michael [USA] [mailto:[EMAIL PROTECTED]
Sent: Friday, November 02, 2007 12:33 PM
To: axis-user@ws.apache.org
Subject: RE: CXF Mtom service and Axis2 Axiom client (FIX)
FYI:
I finally got it working. turns out it is a classpath issue.
I have CXF and Axis2 in the same eclipse project and Java WS clients
written with both frameworks.
I moved the Axis2 WS Client to its own project and now it works.
I am not sure why when the CXF and JAR dependencies and Axis2
