Hurra,
You made it ... it's working with your last commit.
Thanks a lot for your help
Hope you don't break so much in the other part of the code :-)
Guillaume
On 4/17/07, Daniel Kulp <[EMAIL PROTECTED]> wrote:
I have a fix for this that I'm testing now.
In the "unwrapped" case, the unwrappe
Dan
Their service is up and running ... I always perform 2 tests one with
groovySOAP (working with XFire), the other with groovyWS (embedding CXF) and
currently they give different results.
Cheers
Guillaume
On 4/17/07, Dan Diephouse <[EMAIL PROTECTED]> wrote:
Interesting... I will take a peek
Guillaume
Thanks, I always forgot this "mvn clean" ...
OK now it is running but I get 0.0 as result while (which is obviously
wrong) using XFire I got the correct answer i.e. 0.7368 at this time
Cheers
Guillaume
On 4/17/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
Yeah, the API has slightly
I have a fix for this that I'm testing now.
In the "unwrapped" case, the unwrapped parts are sometimes getting an
empty namespace set. That's what your seeing. In anycase, I have a
fix that makes your test work, but I need to find out what else I
broke. :-)
Dan
On Tuesday 17 April 2007
Interesting... I will take a peek into this. I was getting 0.0 back as well,
but I figured it was because their services were broken. I'll get back to
you soon.
- Dan
On 4/17/07, tog <[EMAIL PROTECTED]> wrote:
Guillaume
Thanks, I always forgot this "mvn clean" ...
OK now it is running but I g
Yeah, the API has slightly changed.
A parameter has been changed from List to Collection, which
seems the error you experience.
I would run a clean build by launching
mvn clean install
On 4/17/07, tog <[EMAIL PROTECTED]> wrote:
Hi
There is no problem in sending you this test case. Neverthe
Daniel
Here is my small example. As stated in the previous email, it breaks from
this morning (my time ;-)) so that I can not tell if it still gives a wrong
answer ...
Btw a correct answer is around 0.7 and not 0.0 as it was used to print.
Thanks for your help
Guillaume
---
Hello,
When I send a message to my CXF service using a .NET 2.0 client that is
using WSE 3.0 to enable MTOM capability, I get a server-side stack
trace. It appears it wrongly interprets the content type as: utf-8"
(note the quotation mark).
I've pasted the stack trace as well as the contents of
Ah-- thanks for the tip. I got that configuration from the WIKI:
http://cwiki.apache.org/CXF20DOC/jax-ws-configuration.html
I'll go ahead and edit the page to reflect "-" instead of "_" and leave
the rest (value as a String) since it will be fixed.
-Chris
-Original Message-
From: Dan D
I think I see where the issue might be - we're assuming that the
mtom-enabled property is a Boolean, not a String. As a temporary workaround
you can try this:
true
I'll fix this in SVN as well! (BTW its a "-" not a "_" in the mtom-enabled
property)
- Dan
On 4/17/07, Christopher Moesel
OK, I see the issue. I'll put in a fix for this today. Thanks,
- Dan
On 4/17/07, Christopher Moesel <[EMAIL PROTECTED]> wrote:
Hello,
When I send a message to my CXF service using a .NET 2.0 client that is
using WSE 3.0 to enable MTOM capability, I get a server-side stack
trace. It appears it
Hi
There is no problem in sending you this test case. Nevertheless trying the
last from svn I got the following error:
Caught: java.lang.NoSuchMethodError:
org.apache.cxf.phase.PhaseInterceptorChain.add(Ljava/util/List;)V
java.lang.NoSuchMethodError: org.apache.cxf.phase.PhaseInterceptorChain.add
I am attempting to MTOM-enable my CXF service.
I am using the CXFServlet and Spring configuration.
I have added the following as a child of the element in
the spring config file:
Although my service seems to accept MTOM/XOP requests just fine, it
doesn't seem to be using MTOM for the repo
Just tried it out-- works like a champ! Thanks, Willem!
-Chris
-Original Message-
From: Willem Jiang [mailto:[EMAIL PROTECTED]
Sent: Monday, April 16, 2007 9:34 PM
To: cxf-user@incubator.apache.org
Subject: Re: Service Listing at root of CXF servlet
Hi
This issue was resolved in the r
14 matches
Mail list logo
