Please add the below lines at the head of your server.xml
import resource=classpath:META-INF/cxf/cxf.xml/
import resource=classpath:META-INF/cxf/cxf-extension-soap.xml/
import resource=classpath:META-INF/cxf/cxf-servlet.xml/
So you can get the enough componets to publish the services.
You
Can you show us the detail stack trace and the on wire message?
So we can investigate it.
You can find the tips of debug CXF application in CXF user wiki[1]
[1]http://cwiki.apache.org/CXF20DOC/debugging.html
Willem
-Original Message-
From: bjarnek [mailto:[EMAIL PROTECTED]
Sent:
The importing files are the cxf componets' spring configuration files.
They are in the cxf*.jar's META-INF/cxf/ directory and not in the WEB-INF
directory.
Since your server configuration file has the bus defintions , when the
CXFSerlvet load the bus , it will not load the defualt bus and core
Hi Davide,
You can do it by adding the interceptors with the below codes
JaxWsProxyFactoryBean factory = new JaxWsProxyFactoryBean();
factory.getInInterceptors().add(youInInterceptor);
factory.getOutInterceptors().add(youOutInterceptor);
Willem.
-Original Message-
From: Davide
Hi Davide,
I have no idea about it now.
Maybe you open CXF logger Interceptor to look into the on wire message.
[1]http://cwiki.apache.org/CXF20DOC/debugging.html
Willem.
-Original Message-
From: Davide Gesino [mailto:[EMAIL PROTECTED]
Sent: Wed 12/12/2007 21:28
To:
Hi,
You can take a look at this doc[1] which is useful for working on the JAXB2
annotation.
[1]http://www.caucho.com/resin-3.1/doc/jaxb-annotations.xtp
Willem.
-Original Message-
From: Thorsten Kraus [mailto:[EMAIL PROTECTED]
Sent: Sun 12/2/2007 1:48
To: cxf-user@incubator.apache.org
Hi Jonny,
Which CXF version are you using?
Please try the latest CXF release version 2.0.3.
Since we don't test CXF with Spring 2.5 M1,
please let us know if there is anything wrong when you run the code.
Willem.
-Original Message-
From: Jonny Coombes [mailto:[EMAIL PROTECTED]
Sent:
, Ning (Willem):
If you specify the Spring application context in your web.xml file.
You do not need to touch any of cxf.xml and cxf-servlet.xml.
I admit that CXF provides lots of configuration here.
Willem.
-Original Message-
From: Randy Burgess [mailto:[EMAIL PROTECTED]
Sent: Thu
:[EMAIL PROTECTED]
Sent: Thu 11/15/2007 1:11
To: cxf-user@incubator.apache.org; Jiang, Ning (Willem)
Subject: RE: Monitoring CXF Webservices
Actually I have one last issue...is it possible to not set this up as a
server implememntation but to access it like the other java MX beans?
Eg can I do
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
NO , you do not need to start up the RMI Server explicitly.
Oh, the config file's URI is not match with the code (ManagementConsole.java).
So you need to make sure the jmx server and client's URL are same.
Willem.
-Original Message-
From: Vespa, Anthony J [mailto:[EMAIL PROTECTED]
Sent:
Hi,
I am in Westin Peachtree Plaza and looking forward to having the f2f talk with
you :)
Willem
Hi Tom,
I found Dan Klup's merging email to CXF2.0.x in cxf-commits mail list.
The patch of CXF-1060 should be also in CXF2.0.x branch now.
Please feel free to try the CXF 2.0.3 which is still been voting.
Willem.
-Original Message-
From: Tom Davies [mailto:[EMAIL PROTECTED]
Sent: Wed
Hi
Please see my comments in the mail.
-Original Message-
From: Asleson, Ryan [mailto:[EMAIL PROTECTED]
Sent: Wed 10/24/2007 21:38
To: cxf-user@incubator.apache.org
Subject: CXF First Time User Questions
Hello,
I'm a first time user of CXF. I've used other web service tools in
Hi Benson,
I checked the changes log, the fixing of the jetty engine shutting down did not
catch up the 2.0.2 release.
So you need to try it in the 2.0.3 SNAPSHOT.
Willem.
-Original Message-
From: Benson Margulies [mailto:[EMAIL PROTECTED]
Sent: Sun 10/14/2007 1:12
To:
Hi Jeff,
I do not think the servlet2.5 API is the cause of the error. If I remembered
right,
you told me that you had tried to remove the servlet2.5 API from the war's lib
and it was workable.
Form the stack trace, it looks like the exception is thrown by calling the
WSDL4J extension.
Maybe
Hi Benson
I just tested the web.xml with the Log4jConfigListener and
ContextLoaderListener , they are workable :)
you need to specify the listeners like this:
listener
listener-class
org.springframework.web.util.Log4jConfigListener
/listener-class
Hi
I think you need upgrade the Spring version to 2.0.
CXF internal components configuration is aready the Spring 2.0 formate.
BTW, if you do not use the servlet transport , you can use the CXFBusFactory
instead of SpringBusFactory.
Here[1] are some discussion about it.
Hi,
You need to set the factory with the address that you got from the wsdl
(http://localhost:8080/Service?wsdl).
It must be something like this http://localhost:8080/Service/***;
Willem.
-Original Message-
From: Valerio Schiavoni [mailto:[EMAIL PROTECTED]
Sent: Sat 9/22/2007 0:07
Hi ,
I don't know if it relates to the http header staff(it is the major different
between the http transport and local transport.
I did not write any code about DAO, so may be I am wrong.
Could you send me the stake trace or the work space. May be I can debug it to
find out the real
Hi
You can find the exmple with the https transport in the CXF bin kit's
${CXF_HOME}/samples/hello_world_https directory.
You need set the http:tlsClientParameters to let CXF init the https
connection for your.
You can take the WibbleClient.cxf as an example.
Willem.
-Original
Hi,
You can get the request from the inMessage
HttpServletRequest req = inMessage.get(AbstractHTTPDestination.HTTP_REQUEST);
HttpServletResponse resp =
inMessage.get(AbstractHTTPDestination.HTTP_RESPONSE);
If you could get the inMessage from the exchange in you application code.
Willem.
Hi,
I just went through the DynamicClientFactory code, and found your code got
class loader a little earlier.
When the DynamicClientFactory create the client , it will setup the classpath
to load the generated class.
You just need to use the thread's ContextClassLoader after the
I got what's you want.
I filled a JIRA for it[1]. And You could watch it and try out the snapshots
when I close the JIRA.
[1]https://issues.apache.org/jira/browse/CXF-821
Willem.
-Original Message-
From: Diego Xu [mailto:[EMAIL PROTECTED]
Sent: Fri 7/20/2007 18:38
To:
Hi
From your fault message, I think you need add the below line in you spring
application context.
import resource=classpath:META-INF/cxf/cxf-extension-xml.xml/
Which include the cxf xformat binding for wiring the bus.
Willem
-Original Message-
From: Dale Peakall
Hi Lukas,
You just need set the endpoint address with different port,
Here are the example, if you publish service with jaxws api:
Object implementor = new GreeterImpl();
String address1 = http://localhost:9000/SoapContext/GreeterPort;;
Endpoint.publish(address,
Done.
Here is the URL
http://cwiki.apache.org/confluence/display/CXF20DOC/Standalone+HTTP+Transport
-Original Message-
From: Clough, Samuel (USPC.PRG.Atlanta) [mailto:[EMAIL PROTECTED]
Sent: Tue 7/17/2007 20:39
To: cxf-user@incubator.apache.org
Subject: RE: Getting the HTTP server off
I think you could try to use the endpoint's attribute implementor.
It should be workable with the # convention.
Here is an example for it
jaxws:endpoint id=endpoint1
implementor=#HelloService
address=/services/Greeter1/
Willem
-Original Message-
From: Jacob
Hi Beanson,
My bad to take the JettyHTTPHandler as ContextHandler.
I just checked the Jetty's handler api, and I didn't find a way to get the
parent handler form a childer handler.
Maybe you can find the Context handler by looking up the context path from
server, or we can add the
MayBe you can try the replace the cxf orignal ServiceInvokerInterceptor in the
bus,
You can find ServiceInvokerInterceptor in the
trunk\rt\core\src\main\java\org\apache\cxf\interceptor\ServiceInvokerInterceptor.java
Willem.
-Original Message-
From: Lukas Zapletal [mailto:[EMAIL
Hi Benson,
It's my fault that I missed something about getting the destination from the
transport factory.
It is JettyHTTPTransportFactory and not JettyHttpTransportFactory
The code should be
Bus bus = BusFactory.getDefaultBus();
DestinationFactoryManager dfm =
This is a common issue of the wsdl2java maven plugin,
if you wsdl is very large , the out of memory exception will be thrown.
Please try this
export MAVEN_OPTS=-Xmx512M
Cheers,
Willem.
-Original Message-
From: Benson Margulies [mailto:[EMAIL PROTECTED]
Sent: Thu 7/12/2007 20:49
To:
The key issue that you met is the wsdl and impl class's info are not match yet.
So when CXF tries to build the service model from the wsdl and takes the impl
class information as the reference,
it finds the mismatch of these two types infomation and throws out the
exception.
And I think your
Hi Freeman,
It is not a good idea to add the logging interceptor in this way.
We suppose to use the feature to take care all the complex interceptor setting
things.
In you configuration, you missed the InFaultInterceptors and
OutFaultInterceptors.
Let's use the Ajay's way to set the logging
Hi Richard
Just FYI,
Here are some changes of the configuration of https in the trunk that we did
today.
I just updated the sample of hello_world_https, it should be work with latest
trunk now.
You can take the configurations (*.cxf in hello_world_https) as the examples :).
Cheers,
Willem.
Hi
You can type java -version to get the detail version information.
We now use the lastest jdk1.5 which version is 1.5.11 for development.
You can download the latest jdk1.5 from SUN's website[1].
[1]http://java.sun.com/javase/downloads/index_jdk5.jsp
Hope you enjoy play with the CXF code!
36 matches
Mail list logo
