Guillaume
It could be this: CXF-1168. It has been fixed recently.
And the stacktrace below is probably similar to what you have:
7 ERROR [STDERR]
org.apache.cxf.service.factory.ServiceConstructionException
12:04:26,837 ERROR [STDERR] at
org.apache.cxf.endpoint.dynamic.TypeClassInitializer.beg
thanks!
On 11/13/07, James Mao <[EMAIL PROTECTED]> wrote:
> Jax-ws spec allow you to do this:
>
> ((BindingProvider)port).getRequestContext().put(
>*BindingProvider.ENDPOINT_ADDRESS_PROPERY*,
>"http://foo.com/blah";);
>
> See this thread:
> http://www.nabble.com/Why-does-a-JAX-WS-client-us
I tested with the 2.0.3 RC and it worked. The messages are also logged only
once.
dkulp wrote:
>
> Pierre,
>
> Any chance you could test with the 2.0.3 release candidates that we are
> voting on?
>
> They can be found here:
> http://people.apache.org/~dkulp/stage_cxf/2.0.3-incubator-take1/di
Hi Dan,
I'm always happy to be helpful for discovering bug !
Well maybe there is another bug concerning cxf-codegen-plugin/wsdl2java
maven plugin, adding "-exsh true" option to the plugin leads to a
NullPointerException when generating code.
(note that without "-exsh true" there is no NPE).
He
Back !
After some struggling setting classpath, I've ran successfully wsdl2java ant
tasks within maven with -exsh option set to true, I think there may be some
problem in cxf-codegen plugin since it seems ok with ant and ko with maven.
Code generation is running fine but calling the web service
Hi,
I'm using CXF with JAX-WS, and I do have problems/misunterstandings about
character encodings. Here's my problem. Basically :
1. Server may run on different platforms (Linux, Windows, ...) for which
default charset encodings are different
2. clients are not necessarily written in Java (I do
Joel,
What are your maven dependencies? The -exsh true stuff requires the
cxf-rt-bindings-soap dependency to work. Are you also running via the
exec plugin (or jetty:run)? If so, the lack of a couple dependencies
could also cause some problems.
Make sure you have the cxf-rt-frontend-jax
Hrm, in the servlet I wrote (basically turned that management class into
a servlet) I just get blank output most of the time - it seems like it
maybe one out of ten times it actually returns the endpoint info.
Any thoughts?
-Original Message-
From: Jiang, Ning (Willem) [mailto:[EMAIL PROT
Hi,
I have problems trying to use the Dynamic Client for the web service:
http://www.ncbi.nlm.nih.gov/entrez/eutils/soap/efetch.wsdl.
It throws an exception that I copy-paste at the end of this email. I am
using cxf 2.0.1.
Is that something that could be fixed in future releases of XJC or
Hi Dan,
I already post an answer concerning my maven problem and the ant migration
but it has not yet appeared in the mailing list (I'm using nable web site to
interact on the mailing).
Ant migration solve the maven problems, but for information purpose here's
the dependency section used in my m
I've the same requirements for my services. A session is initialized on the
first call to a services and should be shared with others. On the server
side, I've written Interceptors to fetch and store the session data in
message.getExchange().getSession().
Using soapUI I can manually set the JSESS
I'm not quite following the question here. If you use CXF or a similiar
kit for client and server, it will ship everything everywhere in UTF-8.
What are you using for a client?
> -Original Message-
> From: melix [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, November 13, 2007 8:43 AM
> To:
Hiya,
I would like to know when is due the 2.0.3 release ?
I would prefer to stick to official release rather than SNAPSHOT for GroovyWS.
Thanks
Guillaume
Hello,
I currently have a web service client that is generated through Weblogic
8.1's built in WSDL2Java tool (I think Weblogic's tool is based on Axis
1.x). I want to move away from the Weblogic implementation to a more
modern and robust implementation.
I decided to evaluate both Axis2 and
Can you post the WSDL? Have you tried running your WSDL through CXF's
validator?
Nathan
-Original Message-
From: Asleson, Ryan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 13, 2007 3:04 PM
To: cxf-user@incubator.apache.org
Subject: SoapFault Error
Hello,
I currently have a web
The WSDL is at the end of this message.
How do I use the CXF WSDL validator? I haven't seen any mention of that
-- I must have missed it.
Thank you!!
http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/";
xmlns:s3="http://www.theserviceendpoint.c
Working on it now. It should be in the maven repository in a few
minutes. It's now in the dist dir:
http://people.apache.org/dist/incubator/cxf/
I should have the download page updated shortly and will get the
announcement out once everything syncs.
That is all contingent on the internet c
Am Dienstag, den 13.11.2007, 14:03 -0600 schrieb Asleson, Ryan:
> Once I did that, when I run the test, it fails with this error:
>
> org.apache.cxf.binding.soap.SoapFault: Server did not recognize the
> value of HTTP Header SOAPAction: .
>
> I can't for the life of me figure out what might be
It's the "-validate" option when you run wsdl2java. It's listed here:
http://cwiki.apache.org/CXF20DOC/wsdl-to-java.html
Glen
Am Dienstag, den 13.11.2007, 14:17 -0600 schrieb Asleson, Ryan:
> The WSDL is at the end of this message.
>
> How do I use the CXF WSDL validator? I haven't seen any me
Hello,
I'm slightly confused on when interceptor chains[1] are created. The
text gives sections on "On the incoming chains, you'll have the
following phases" and "On the outgoing chain there are the following
phases", but I'm unsure what incoming and outgoing refer to.
Is it:
1.) Only with resp
Hi Glen, this applies to both client side and server side. Incoming and
outgoing refer to inbound and outbound. If this is still not clear, on the
client side, incoming refers to receiving response from the server, outgoing
refers to sending request to the server.
Cheers,
Jervis
> -Origina
Hi Glen,
I think the interceptor chains are sorted by the message flow's direction.
One is for incoming message , it could be the response message in client
and the request message in server; the other is outgoing message which could
be the request message in client and response message in serv
And yes, there are four chains, the outgoing chain and the incoming chain for
the same client can be totally different.
Jervis
> -Original Message-
> From: Glen Mazza [mailto:[EMAIL PROTECTED]
> Sent: 2007年11月14日 8:42
> To: cxf-user@incubator.apache.org
> Subject: when are interceptor ch
Hi,
I think firstly, you have to make sure that the wsdl is valid, from the
error message, it clearly said that the
"Value" is already defined.
So I guess probably we have to check the schemas imported/included in the wsdl.
I know there's no joy in reading the xml/schema :(
Regards,
James
24 matches
Mail list logo
