Hi,
Having this issue while deploying CXF in Tomcat which has
SecurityManager enabled and can't turn off.
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'helloWorld': Invocation of init method failed; nested
exception is
);
Is it applicable to SOAP 1.2 ?
Thanx
-yogen
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 24, 2008 10:58 AM
To: cxf-user@incubator.apache.org
Cc: Yadav, Yogendra (IT)
Subject: Re: SOAPAction Http header
With SOAP 1.1, SOAPAction is REQUIRED
Hi,
Anybody's has used CXF-Plugin, want to share your experience ?
Does anybody know if this plugin will make it to production ? And if
this will be available as a standard Eclipse plugin with Features and
Site.xml
Thanx
-yogen
-Original Message-
From: Yadav, Yogendra (IT)
Sent: Friday
PM
To: cxf-user@incubator.apache.org
Cc: Yadav, Yogendra (IT)
Subject: Re: WSDL retrieval at runtime, is it required?
It's not totally required.You CAN call the service constructor
passing null for the wsdl and it should create the service fine.
You'll need to manually set
Hi,
I have already used wsdl2java -client to generate client code to
access a CXF service. The WSDL that I provided does include service
endpoint information. I see that, now at runtime the client code tries
to retrieve the WSDL again (see the stacktrace below), why? Does it only
do it to extract
Hi,
I am trying to configure the Jetty thread pool. Looked at this page and
started configuring Jetty thread pool.
http://cwiki.apache.org/CXF20DOC/jetty-configuration.html
I created a config file called cxf-jetty-config.xml. Put this in
classpath and started my service with command line arg as
Hi,
I have configured / published the POJO service endpoint class using
JAXWS Endpoint API. I am providing executor thread pool to the Endpoint.
I don't see the executor thread pool being used by runtime. All I see is
Jetty transport threads in debugger in EclipseIDE.
POJOClass c = new
