Guillaume,
I deployed a new 2.0.4 snapshot.
I made another change. I discovered in my testing that the idea of:
invoke(String op, boolean unwrapped, Object ... params)
pretty much sucks.If the first param is supposed to be a boolean, it
gets all confused and stuff. Thus, I reverted
Hi Dan,
This is ok, I looked at your code, I was doing similar things in my
GroovyWS client. Keep me informed when the snapshot will be published
?
Btw, the current snapshot give me this exception ... Am I doing
something wrong when creating my client ?
Cheers
Guillaume
Hi Guillaume
The exception is caused by my patch for removing
@Resource(name = activationNamespaces)
to support Spring 2.5.
I did a quick fixing for it few days ago , so the exception will go way
when you get the latest snapshot.
BTW,
This exception only happened when your are useing
Ok willem, I will get the latest snapshot.
Thanks for the info
Guillaume
On Dec 6, 2007 9:48 AM, Willem Jiang [EMAIL PROTECTED] wrote:
Hi Guillaume
The exception is caused by my patch for removing
@Resource(name = activationNamespaces)
to support Spring 2.5.
I did a quick fixing for it
Hi Dan and Glen,
Object[] response = client.invoke(GetTeamInfoByCity, obj);
to something like:
BindingOperationInfo bop = ... lookup operation from service model
Object[] response = client.invoke(bop, ID, PASS, New England);
then it SHOULD work. The trick is getting the bop.I
Guillaume,
If you call the:
BindingOperationInfo op =
client.getEndpoint().getEndpointInfo().getBinding().getOperation(operationName);
to get the operation, there is a op.getUnwrappedOperation(). If that
is not null, if you invoke with the string name, it will expect it to be
unwrapped as
Guillaume,
I've honestly never seen that error before. However, it MIGHT have
something to do with wrapped/unwrapped styles internally. Internally,
it may be expecting it to be in unwrapped form, thus expecting 3
strings instead of a GetTeamInfoByCity object.
Dan
On Saturday 01
Guillaume,
Did some more digging.This is related to:
https://issues.apache.org/jira/browse/CXF-885
Basically, the GetRemainingHits is killing things. As soon as CXF
sees a method that is not wrapped/wrappable, CXF doesn't add any of the
interceptors for the wrapped cases. :-(For
Am Montag, den 03.12.2007, 14:17 -0500 schrieb Daniel Kulp:
Guillaume,
Did some more digging.This is related to:
https://issues.apache.org/jira/browse/CXF-885
Basically, the GetRemainingHits is killing things. As soon as CXF
sees a method that is not wrapped/wrappable, CXF
I don't know anything about GroovyWS; you may wish to check with them on
the problem. As you can see from the blog entry, using Java, both CXF
and Metro works fine with the web service, so our job is done.
Perhaps if you configure GroovyWS to use Metro instead you will get a
different error
Hi all,
Following the tread on the dynamic client, I was reading a post by
Glen (http://www.jroller.com/gmazza/date/20070929), when I decided to
give the NFL strike iron webservice a try with GroovyWS.
The fact is that both the web service and cxf are working ... so I
must be doing something
11 matches
Mail list logo
