Yeah, It's ten years. Happy birthday CXF.
It's my pleasure to be part of this project.
Willem Jiang
On Tue, Apr 17, 2018 at 7:06 AM, Freeman Fang
wrote:
> Wow, ten years, time flies! We should have a beer together, remotely, ;)
>
> I am so grateful and proud that I am
Hi,
You just need to setup the address which is start with "netty://" just like
“netty://http://localhost:9000/SoapContext/"; and make sure you put the
cxf-rt-transport-netty-server and cxf-rt-transport-netty-client into the class
path.
I will add an example for it.
--
Wi
/LoggingOutInterceptor.html
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On June 24, 2014 at 3:33:30 PM, bimjoeipa (joel.pear...@ipaustralia.gov.au)
wrote:
>
://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324786&projectId=12311211
On behalf of the Camel PMC,
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
Maybe something is wrong with the Spring setting.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On March 19, 2014 at 4:33:06 PM, rn@dev (rakeshramachandrann
Can you double check the setting of SSLSocketFactory is right?
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On March 19, 2014 at 1:51:52 PM, rn@dev
httpConduit.setTlsClientParameters(tlsCP);
Than
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On March 19, 2014 at 5:29:37 AM, rn@dev (rakeshramachandrann...@gmail.com)
wrote
What kind of error did you get?
Did you put the cxf-rt-http-jetty jar into you class path?
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese
Can you double check if there different version of CXF jars in your class path?
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
Twitter
I think you need to put cxf-rt-bindings-soap.jar into your class path.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter
If you don't setup the interceptor on the Bus, I think it should be safe to
share the same bus within these two camel context.
BTW, you can only set the SSL configuration on one port, no matter if they use
the same bus or not.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Hi,
You cannot assume that different bundles are not share the same thread in
ServiceMix.
You need to create a new bus to avoid the side effect of share the bus in
different bundle.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http
Hi,
You can configure the parameters with [1]
[1]http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html#ClientHTTPTransport%28includingSSLsupport%29-The%7B%7Bconduit%7D%7Delement
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http
It looks like build need the internet access.
Maybe you need to setup the proxy on the maven option.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http
deployment-structure.xml file.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.j
Can you changed the surfier fork mode and make sure the JAXWS server is start
per class?
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English
Hi,
Did you try to use the apache snapshot maven repo?
The url is https://repository.apache.org/content/repositories/snapshots.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http
Hi,
The response should be a valid soap message which is wrapped with the
.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English
Hi ,
You can set the http-conduit for certain endpoint just by set the name as
portQName.http-conduit.
For example http://widgets/widgetvendor.net}widgetSOAPPort.http-conduit";>
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.co
Can you let the CxfServlet initialize first?
I don't think camel-cxf can start rightly when the transport layer is not ready.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com
Hi,
How did you start the camel context?
Did you start it before deploying the CxfServlet ?
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com
Hi,
Can you access these three services with the addresses those you published?
It looks more like a services registry issue.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http
Hi,
Can you try to look at the JAXWS Dispatch API[1]?
It could be more easy to deal with the XML message with this API.
[1]http://cxf.apache.org/docs/jax-ws-dispatch-api.html
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http
IBM JDK will perform the GC proactively. I think we should be able to fix this
issue as the mail thread tells.
Did you have chance to try to use the latest CXF version ?
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
You doesn't use the ClientProxy rightly, as the client proxy will be GCed
(there is no reference of HelloWorldPortType port any more) when the
initClient() is called.
Please just use the port directly when you invoke the service.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part o
Using the maven could save you lots of time for noodling the third part
dependencies ;)
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English
Hi,
Can you check if you put the cxf-rt-bindings-soap-2.7.3.jar into the class
path?
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English
("8bit");
transportHeaders.put("Content-Transfer-Encoding", value);
requestContext.put(Message.PROTOCOL_HEADERS, transportHeaders);
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://will
Can you try access the wsdl file with a browser?
In this way, we could check if there is something wrong on the server side.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http
On Monday, October 22, 2012 at 6:16 PM, Glen Mazza wrote:
> (resending...)
>
> On 10/21/2012 10:51 PM, Willem jiang wrote:
> > PubSub is important for the us to implement the failover mechanism.
> > Although there could have multiple service listen to request, we can
and listener
container to send and receive the message, we don't need to care much about the
if the destination is topic or the queue. So we can still implement the
Request-Response MEP with JMS using PubSub.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web:
easily.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Here is the thread[1] for it.
[1]http://cxf.547215.n5.nabble.com/add-namespace-to-soap-header-td5716003.html
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http
the latest one?
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese)
Twit
efore you
publish the endpoint of "uus"
BTW, which version of CXF are you using ?
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
Can you show us the dependency tree of your project ?
Did your project has the dependency of the cxf-rt-bindings-soap module?
On Sat Jun 23 05:49:45 2012, Benson Margulies wrote:
INFO: Creating Service
{http://jdd.basistech.com/}DocumentDatabaseService from class
com.basistech.jdd.DocumentDataba
Hi Benson,
CXF JMS transport depends on the spring-jms, but you don't need to use
Sping for the configuration of soap over jms implementation.
On Thu Jun 21 09:07:07 2012, Benson Margulies wrote:
http://cxf.apache.org/docs/jax-ws-java-first-with-jms-transport.html
says that it's obsolete.
Bu
Maybe you can setup some kind of proxy to delegate the request to a right
service.
In this way CustomerB service will not be accessed by CustomerA.
On Sun, Jun 3, 2012 at 6:02 AM, Christian Müller <
christian.muel...@gmail.com> wrote:
> Hello Sergey, hello Dan!
>
> Thanks for your responses. In
Hi
Which version of JDK are you using ?
If you are using JDK 1.6, you may need to do some addtion work to
resolve the issue.
On Tue Mar 20 19:25:54 2012, merve wrote:
jaxb-api-2.2.3 and jaxb-xjc-2.2.4-1 are coming with apache-cxf-2.5.2. Firstly
I used them. After your message I downloaded pr
Hi,
How did you deploy the service ?
If you are using the embedded jetty engine which is provided by
cxf-transport-http-jetty module, you can not set the DoSFilter on it.
If you are deploy the service with help of CXFServlet, you can leverage
the DoSFilter feature of the WebContainer.
Willem
From my experience of writing camel-cxf[1] component, I think you just
do the basic part of the integration which can marshal and unmarshal the
request and response. You just delegate the servlet transport to JAXB
data binding.
As you know CXF has lots of interceptors which provides a great
e
Hi Yogesh,
Your case is different, as you are not using the camel transport for
CXF, so you can't get any camel exchange from the message context.
As you are using the one way operation camel may not get the exception,
I will need to write a simple test case to dig the code for it.
On 2/17
Hi Beanson,
It makes our life easier by using the message broker which decopes the
request and response side.
I don't think it's good idea to implement an executor which behavior is
bund to the queue size.
It could much easy to let the message broke reject the request when the
queue is ful
I guess you just use the SS to protect the URI. It could be easy to
add another filter on the SS side to map the exception.
On Wed Feb 1 22:54:39 2012, gigi shea wrote:
Hi, Sergey,
thank you so much for the reply. You are right, SS is added as a chain of
filters to accomplish authentication
On Thu Jan 12 00:10:54 2012, Benson Margulies wrote:
I'm trying to sort out the various sources of multi-threadedness when
have a JMS endpoint launched from java. I'm having some trouble
interpreting the email from Freeman quoted, and then I pasted my
launch code.
One way to interpret Freeman's
Hi,
Yes, you can set the feature as the spring does in Java code.
On Thu Jan 12 00:07:04 2012, Benson Margulies wrote:
What's the following in Java? Create a JMSConfig object and then add
it as a feature?
http://customerservice.example.com/";
serviceName="customer:CustomerServiceSer
hich configure two seperate
services. But the cxf actually do is just publish two service, and each service only
activate one port; I cannot got a wsdl which activate two port simultaneously?
Glen
On 12/28/2011 04:07 AM, xuhb wrote:
- Original Message -
From: "Willem Jiang&qu
In this case you need to specify the two endpoint and publish them
separately.
The port of the wsdl is band to the CXF endpoint, you may need to do
some addition work to check the WSDL if you want to publish the service
from the WSDL automatically.
On 12/28/11 3:53 PM, xuhb wrote:
Thanks wi
Hi,
I didn't quite get your meaning. CXF should support this kind feature
long time ago.
You can specify the endpoint Qname of the WSDL when publish the service
from CXF. It means CXF supports to create the service module from the
WSDL which has multiple ports.
On 12/27/11 12:12 PM, xuhb w
It could be easy if we just hack the Soap11FaultOutInterceptor and
Soap12FaultOutInterceptor
to deal with special exception which is throw from the user
interceptor.
On Tue Dec 27 18:09:51 2011, Son Tung Nguyen wrote:
Hi kobol,
I think you can put a flag in WebserviceContext object and contin
Hi,
You need to do some work on the ClientFaultConverter to turn the
ApplicationFault to the exception which the client proxy can be thrown.
xmlns:i="http://www.w3.org/2001/XMLSchema-instance";>
System.NullReferenceException
On Thu Dec 15 19:29:38 2011, simran wrot
Hi,
You may need to add a customer interceptor to interpret the detail message.
You can find some information here[1], and you need also take a look at
the code of org.apache.cxf.interceptor.ClientFaultConverter[2]
[1]http://willemjiang.blogspot.com/2011/01/how-to-map-soap-fault-message-with.
Hi,
Maybe there are more than one version of @WebService.
I'm not sure that the Single bundle of the Dosgi has the @WebService
class. But you may also check if the System bundle also export that kind
of package.
On Wed Dec 14 23:20:19 2011, DMoniX wrote:
I'm quite new to CXF so bear with m
Hi,
Oh, I need to take a look at how you create the CXF client proxy.
The server side is looking good.
On Tue Dec 13 17:55:08 2011, drslim wrote:
To follow my last message...
SEI (Service Endpoint Interface)
Spring declaration is :
Hi,
You can find some information about it here[1]
[1]http://willemjiang.blogspot.com/2011/01/how-to-map-soap-fault-message-with.html
On 12/12/11 7:59 PM, Malisetti, Ramanjaneyulu wrote:
Hi
we have the following code to create SoapFault for sending server side
exception to client. On
How did you create the CXF client ?
Can you make sure the SEI is set rightly?
On Tue Dec 13 17:06:23 2011, drslim wrote:
Hi there,
I've got this error when trying to access a CXF Webservices using a JUnit
test. The WSDL is accessible and the service seems to be working.
Below the error :
Yes, my blog explain when we should move the new Jetty7 implementation :)
BTW, CXF also support the continuation API which provides by Servlet3.
If you are consider Tomcat7 and Jetty8, you need to take a look at it.
On Tue Dec 13 10:28:00 2011, ramesh wrote:
On 12/12/2011 08:04 PM, Willem
Hi,
camel-cxf is leverage the continuation which is provided by Jetty7.
As the CXF has it own continuation wrapper, there is no much pain, when
we move from Jetty6 to Jetty7.
On Tue Dec 13 06:14:26 2011, ramesh wrote:
Is CXF Continuations tested for Jetty 7 ?
I have this doubt because Continu
Does the third party application has the schema or WSDL for the XML?
On Fri Nov 11 08:45:05 2011, amathewcxf wrote:
Hi,
We have an application where we need to communicate to a third party
payment system. The company which does the payment system provided an XML
document which we need to s
CXF supports to publish the services without help of the servlet
transport. For your case, you just need to use jaxws:endpoint,
jaxrs:server to define the endpoints with full address.
On 10/26/11 1:36 AM, cogitate wrote:
is it possible to bootup cxf components in a spring container having jax
Hi,
It's is a interesting test requirement.
As you know CXF using the LocalTransport to avoid using the network
during the unit test.
If you just want to test the interceptor in unit test, it could be more
straight if you just mock a message with the Stream that you want to
feed in.
On Tue
It's a spring annotation instead of cxf one.
On Tue Oct 25 23:36:54 2011, David Karlsen wrote:
You can try
http://static.springsource.org/spring/docs/2.5.5/api/org/springframework/remoting/jaxws/SimpleJaxWsServiceExporter.html
to export the beans.
2011/10/25 zujing:
I'm using CXF with Spring
camel-cxf producer will use the async invocation by default, It's more
like an issue of CXF client async invocation.
It could be more helpful if you can show us the stack trace or where
the code is blocked.
On Fri Oct 14 16:42:24 2011, xuhb wrote:
Sorry forget to say proxy:
the proxy act as a w
You can use below code to tell if the messsage is from client.
Boolean.TRUE.equals(message.get(Message.REQUESTOR_ROLE))
On Fri Sep 30 17:40:10 2011, Gerald Preissler wrote:
I'm implementing an interceptor for CXF and am looking for a way to
programmatically determine where the interceptor is ac
You can access the WSDL with is generated from the CXF service from this
url http://localhost:8080/trainCFX/HelloWorld?WSDL.
I just have a quick look at the AxisClient, it looks it still use the
JAXRPC API which is replaced by JAXWS. That could explain why you
AxisClient can get the right resp
sport ?
- Original Message -
From: "Willem Jiang"
To:
Sent: Wednesday, September 28, 2011 5:35 PM
Subject: Re: Caused by: java.net.SocketException: Unexpected end of file from
server
Just one comment for the maxIdleTime. Jetty use this parameter to check
the underlayer strea
cxf-servlet.xml will be loaded by CXFServlet for publishing the endpoints.
On Wed Sep 28 15:30:46 2011, Christian Schneider wrote:
Hi Arambage,
cxf-servlet.xml is a spring config to start the cxf endpoint as a
servlet in a container. I just checked the java_first_jaxws demo.
I could simply remo
Just one comment for the maxIdleTime. Jetty use this parameter to check
the underlayer stream's states,
the timeout timer will be reset when there is any read or write
operation on the stream.
On Wed Sep 28 13:39:03 2011, Freeman Fang wrote:
Hi,
I've encounter similar exception lately(with Cx
It will be hard if you has a bunch of interceptors to configure.
CXF Feature gives you a way to configure the interceptors into Server,
Client or Bus easily.
If you just has one Interceptor need to be use, you don't need to use
the feature :)
On 8/28/11 6:54 PM, Raj Floyd wrote:
Hi,
Are Fea
Hi
Can you try to use the latest released CXF 2.3.6 ?
If I remember right, there are some soap with attachment bug fixings
recently.
On Thu Aug 25 02:10:59 2011, robbywillz wrote:
Hi,
When my CXF client receives big attachment, the DataHandler object returns
the empty content. But similarly
You add xml is not a pull json file.
It has some xml tags, you need to clean it up.
On 8/24/11 3:21 PM, yyc178 wrote:
interface :
@WebService
public interface UserManager {
@Post
@HttpResource(location="/saveUserByPost")
@Produces("application/json");
public void saveU
You can also call the bus.shutdown() to shutdown the Jetty server.
On 8/24/11 7:43 AM, Dennis Sosnoski wrote:
When I create a JAX-RS server and run it in process with the following code:
JAXRSServerFactoryBean sf = new JAXRSServerFactoryBean();
sf.setServiceClass(LibraryRestIm
all in one jar sometime will cause troubles if the other lib has same
third part dependencies which is not use the all in on jar.
BTW, all in one jar is not convince for the people who don't want to
include the whole Spring framework for a single part JMX annotation class.
On 8/24/11 2:50 AM,
You should put the endpoint and client in the same application context.
The LocalTransport is attached to the bus, now your endpoint and client
are using different bus.
On 8/23/11 8:28 PM, mymacin wrote:
Hi,
When I try to use Local Transport instead of Http I am getting the below
exception.I
As CXF jaxws:endpoint just try to get the reference of myServicePortType
once, even you defined the bean of myServicePortType to be prototye, the
MyServicePortTypeImpl just is just created once.
If you want to make the implementor to Non singleton, you may need to
create a new Invoker[1] yours
3 but changing to 2.4.0 fixed the issue. Which files
shouldn't I need to import?
Still strange though - I left the imports in beans.xml but there still
aren't any physical files anyway, are these being stepped over by CXF
and defaults applied?
-Original Message----- From: Willem Jiang
Hi,
It looks like you are using CXF servlet transport.
Please make sure you put the cxf-core into the class path.
Which version of CXF are you using ?
If you are using CXF 2.4.x, you don't need to import all the below
resource.
On Wed Aug 10 06:09:44 2011, David G wrote:
I had a jax-ws service
oting Willem Jiang :
Yes, it is possible.
You can using JaxWsServerFactoryBean to publish the service or stop the
server as you want.
You can find more information here[1]
[1]http://cxf.apache.org/docs/a-simple-jax-ws-service.html
On 8/6/11 9:04 AM, john.dun...@exceter.com wrote:
I'd lik
Yes, it is possible.
You can using JaxWsServerFactoryBean to publish the service or stop the
server as you want.
You can find more information here[1]
[1]http://cxf.apache.org/docs/a-simple-jax-ws-service.html
On 8/6/11 9:04 AM, john.dun...@exceter.com wrote:
I'd like to embed CXF in a way
Hi
CXF using XMLBeans to as a third part lib to provide the data binding,
just like the JAXB.
I think you should ask the developement question in the XMLBeans mailing
list.
On 7/30/11 12:23 PM, c...@gliesian.com wrote:
I noticed that CXF has support for Apache XMLBeans.
I'm trying to figur
There were some http related refactoring in CXF 2.4.0.
But from the exception it looks like the you didn't install a right CXF
bundle.
Maybe you need to update your application context for it.
On 7/20/11 3:26 PM, Lars Heppler wrote:
Hi,
for me it does not work with the latest version of cxf 2
If you are using the CXF-Servlet to load the Application, CXF just
create a XmlWebApplicationContext based on the location parameter.
If you are using spring ContextLoaderListener, it will application
configuration files according the ContextLoader. Can you check if your
war has some other app
Hi,
Did you put the cxf-rt-transport-http-jetty jar into your class path ?
If you are using mvn, you can use mvn dependency:tree to check with it.
On Tue Jul 12 04:52:09 2011, KARR, DAVID (ATTSI) wrote:
I had a service with unit tests utilizing JAXRSServerFactoryBean. I believe it
was using C
You don't need to have the below line in your configure file.
On 6/24/11 9:24 AM, Freeman Fang wrote:
Hi,
Cxf bus refactor a lot since cxf 2.4.0.
In your spring configuration
is unnecessary
and you need change
to something like
Freeman
On 2011-6-24, at 上午12:44, Sonam Nepali wrote:
Hel
Why are you using CXF 2.0.4-incubator?
Can you use some latest version of CXF?
BTW, CXF 2.0.x, CXF 2.1.x, CXF 2.2.x are retired from Apache CXF so far.
On 6/21/11 12:45 PM, siuyab wrote:
Dear all,
I am developing a cxf web service client with simple username token
authentication. Before using
It's hard to know what the exactly the services address is when you
start the the endpoint in the servlet or osgi container.
The address will be changed if your war or servlet configure is changed.
If you already know the physical address, you may consider to use
publishedEndpointUrl property t
Can you try to lookup the xmlschema*.jar in the JBOSS lib ?
On 6/17/11 8:19 PM, Stiffler07 wrote:
Hi Freeman,
how can I check this?
regards,
Stephan
--
View this message in context:
http://cxf.547215.n5.nabble.com/consuming-dynamic-client-in-glassfish-NoSuchFieldError-QUALIFIED-tp4496629p44
Hi,
If you want Jetty listen to all the network interface you do use this
0.0.0.0:PORT.
On 6/17/11 12:56 AM, Vitaly Peressada wrote:
Migrated from
CXF 2.2.2 and Jetty 6.1.18
To
CXF 2.4.0 and Jetty 7 7.3.1.v20110307
We start CXF using JAXRSServerFactoryBean something like:
this.endpointUrl =
The default receive time is 6 ms which means 60 second.
You are setting the timeout to be 36 seconds :)
On 6/16/11 9:58 PM, Blue Diamond wrote:
CXF Version used is 2.3.0.
On Thu, Jun 16, 2011 at 6:40 PM, Malisetti, Ramanjaneyulu<
ramanjaneyulu.malise...@ca.com> wrote:
Hi,
I have
No, JAX-WS handlers are configured per endpoint.
On 6/16/11 4:34 AM, Gunnar Morling wrote:
Hi,
according to the documentation [1] one can specify interceptors on the
bus level, which will then be applied to all endpoints. Is the same
also possible for JAX-WS handlers?
Thanks, Gunnar
[1] http:
Hi
I did some work to fix get the test work.
I had no luck with fixing the jetty-beans.xml, so I wrote some java code
to start the jetty server like this. You need to make sure the servlet
is using the same bus with the jaxws endpoint that you publish thought
the spring config.
public class
Current Camel transport for CXF just provides a transport tunnel for use
to use. It can't handle the exception that comes from the service
implementation.
If you want the camel to handle the application exception, you may
consider to use camel CXFBean[1] components. BTW you had to marshal the
Hi ext2,
I just checked the HTTPConduit code,
It checks the response code before checking the MEP, maybe you need to
try the latest CXF code.
if (responseCode >= 400 && responseCode != 500 &&
!noExceptions) {
throw new HTTPException(responseCode,
connection.getRes
On 5/27/11 9:43 PM, mymacin wrote:
@Willem.Jiang
I want to make it work with spring Transaction with JMS . I have one doubt
on this ,is it possible to combine JMS transaction and spring JPA
transaction at the same time?
I think you can do a simple test by throwing an exception in your
applic
Hi,
I just found you want to combine the JMS transcation and JPA together.
Not sure if these two resource can work together with the JTA
transaction manager.
On 5/27/11 6:14 PM, mymacin wrote:
Here is my spring bean configuration
Yes, just as Dan said you can use camel-mina/camel-netty to implement
the tcp transport and route the message into CXF by using the camel
transport of CXF without much work.
But you still need to some work to mapping the transport level headers
between the CXF message context if you want to impl
Because of the HTTP keep alive feature, if you close the socket and
start a new socket which listen to the same port in the same process,
you may face an issue that new start socket can't accept the request
anymore.
Normally you can start the server before the test class is load and
shutdown
Sorry, I click the send button too quickly to find some typo in my mail.
Hi Dan,
I just a quick question for it. Does CXF has a chance to identify the
jaxax.ws package missing import situation ?
How about throw some warning message when CXF cannot find the
@WebService annotation when the use
Hi Dan,
I just a quick question for it. Does CXF has a change to identify the
jaxax.ws package missing import situation ?
How about throw some warning message when CXF can find the @WebService
annotation when the user is using the JAXWS API to create the endpoint ?
On 5/24/11 11:44 PM, Dani
On 5/24/11 7:56 PM, Michael Täschner wrote:
52 ACTIVE org.apache.cxf.bundle-minimal_2.3.4
Can you replace this bundle with org.apache.cxf.bundle ?
I'm not sure if this issue is caused by the minimal bundle.
--
Willem
--
FuseSource
Web: http://www.fuse
1 - 100 of 266 matches
Mail list logo