A defect of JAXWS of RPC Literal operation which has xsd:Element message part?

Hi: CXF support RPC Literal operation which has message part point to a xsd:element; But it seems there is a defect; First I generate a JAXWS interface from such a wsdl, and publish the JAXWS as service; If I doesn't specifiy the origical wsdl's location and force CXF create

Re: A defect of JAXWS of RPC Literal operation which has xsd:Element message part?

By the way, I am not sure if JAXWS specification support a RPC-Literal Operation whose message part point to a xsd:element, not to a xsd:type. Does anyone know about it ? - Original Message - From: xuhb x...@tongtech.com To: users@cxf.apache.org Sent: Monday, January 16, 2012 5:17 PM

Re: A defect of JAXWS of RPC Literal operation which has xsd:Element message part?

Thanks Dan. Thanks your help; - Original Message - From: Daniel Kulp dk...@apache.org To: users@cxf.apache.org Cc: xuhb x...@tongtech.com Sent: Monday, January 16, 2012 11:51 PM Subject: Re: A defect of JAXWS of RPC Literal operation which has xsd:Element message part? On Monday

Re: Does CXF support multiple endpoint for single wsdl now?

-WS compliant.) Be careful what you wish for. :) Glen [1] http://www.jroller.com/gmazza/entry/web_service_tutorial#WFstep6 [2] http://docs.oracle.com/javase/6/docs/api/javax/xml/ws/Endpoint.html On 12/28/2011 09:03 AM, xuhb wrote: - Original Message - From: Glen Mazzagma

Re: Does CXF support multiple endpoint for single wsdl now?

. It means CXF supports to create the service module from the WSDL which has multiple ports. On 12/27/11 12:12 PM, xuhb wrote: Hi: I remembered old version CXF doesn't support multiple port(endpoint) for single service of wsdl. Does the latest version support this feature? Thanks any

Re: Does CXF support multiple endpoint for single wsdl now?

service to support mult-port, because if so, the invoker may not binding to service, it should be binding to port or endpoint; On 12/28/11 3:53 PM, xuhb wrote: Thanks willem and Glen: I have tried, it seems I can only make CXF to publish a service with single port , I still cannot make CXF

Re: Does CXF support multiple endpoint for single wsdl now?

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 Jiangwillem.ji...@gmail.com

Re: Does CXF support multiple endpoint for single wsdl now?

Thanks willem and Glen: I have tried, it seems I can only make CXF to publish a service with single port , I still cannot make CXF to publish a service with multi-port taking effect at same time; Also I have tried the example of CXF systest which support

Does cxf support xsd:any?

Hi: I am using camel 's payload CXF component; Now I want publish a service which doesn't constraint any xml schema, and client can post any xml element to this webservice; so I define the wsdl which input message's element is xsd:any; it looks like: wsdl:message name=anyRequest

Concurrent Problem of CXF on tomcat?

Hi: I build a simple proxy with cxf(2.4.3) camel(2.8.1) on tomcat, and trying to test the performance with HP LoadRunner; the proxy program is build with pay-load model of camel-cxf; If the concurrent client is only 1, there is nothing wrong, the throughput capacity is very stable

Re: Caused by: java.net.SocketException: Unexpected end of file from server

Thanks for William Jiang. I also encounter such a problem. maxIdleTime works well; Will cxf support to configure maxIdleTime for jetty-transport ? - Original Message - From: Willem Jiang willem.ji...@gmail.com To: users@cxf.apache.org Sent: Wednesday, September 28, 2011 5:35 PM

A question about CXF chain interceptor mechanism

Hi: CXF Chain Interceptor is simple and good mechanism for protocol interpret; But sometimes it seem Chain Interceptor mechanism is not very suitable for things such as system resource release; To illustrate this, following is a sample: 1) Recently I am using CXF to expose an existing

Re: A mysteriously deadlock of CXF OnewayProcessorInterceptor

Thanks Dan: I tried, it's ok now; thanks to your rapid fix; - Original Message - From: Daniel Kulp dk...@apache.org To: users@cxf.apache.org Cc: xuhb x...@tongtech.com Sent: Saturday, August 20, 2011 1:21 AM Subject: Re: A mysteriously deadlock of CXF OnewayProcessorInterceptor I

Re: A mysteriously deadlock of CXF OnewayProcessorInterceptor(A question about CXF chain interceptor mechanism)

Hi, Dan Unfortunately, the fixed for CXF-3750 may cause another question. which I am not sure if it's a issuem of CXF or things the user should take care; Details I have comments in CXF-3750; - Original Message - From: xuhb x...@tongtech.com To: users@cxf.apache.org Sent: Monday

Re: A mysteriously deadlock of CXF OnewayProcessorInterceptor

Maybe it is becuase before chain.wait() return, the sync of chain will be re-locked, so it will block untill chain.resume() finished; - Original Message - From: xuhb x...@tongtech.com To: users@cxf.apache.org Sent: Friday, August 19, 2011 1:39 PM Subject: Re: A mysteriously deadlock

A mysteriously deadlock of CXF OnewayProcessorInterceptor

Hi: Recently when I am checking/testing CXF , there is a mysteriously deadlock of CXF Oneway Process; Normally CXF engine will invoke the one way bussiness logical asynchronized ,, so the servlet handle will finished and return back to servlet engine immediately; But sometime, I

Re: A mysteriously deadlock of CXF OnewayProcessorInterceptor

Sorry, I foget post the issue link: https://issues.apache.org/jira/browse/CXF-3750 - Original Message - From: xuhb x...@tongtech.com To: users@cxf.apache.org Sent: Friday, August 19, 2011 1:34 PM Subject: A mysteriously deadlock of CXF OnewayProcessorInterceptor Hi: Recently when

Re: NULL Pointer Exception while processing attachments

Receiver: users@cxf.apache.org : Re: NULL Pointer Exception while processing attachments On Tuesday, August 09, 2011 11:36:56 AM xuhb wrote: Thanks Jim I just tried the latest version of CXF 2.4.1. This problem doesn't occurs in this version; I think maybe some issue fixed in 2.4.1 has fix

NULL Pointer Exception while processing attachments

Hi: When I use cxf webservice at following situation, there always a null pointer exception occurs 1)MTOM enabled, and multi attachments sent. 2)The first attachment is big enough (etc 2M). and the second attachments is very small (etc: several bytes); 3)the MTOM attachment is mapped to a byte[]

Re: NULL Pointer Exception while processing attachments

Receiver: users@cxf.apache.org Subject: Re: NULL Pointer Exception while processing attachments From the information you provided, we can not tell if it's really a CXF issue. Can you file a jira issue with your test case to help reproduce ? Cheers Jim On Tue, Aug 9, 2011 at 10:43 AM, xuhb x

Re: Does CXF support Webservice Http binding?

=classpath:restful.wsdl bindingId=http://apache.org/cxf/binding/http; On Sun, Jul 17, 2011 at 3:54 PM, xuhb x...@tongtech.com wrote: Hi: Axis2 .net could publish a PortType with Http-Binding in WSDL. That's to say: when user write a service business logical, the user could choose to publish

Does CXF support WSDL1.1 HTTP-Binding?

Hi: When I got a WSDL which contains a HTTP-BINDING. 1)Could I write a client to invoke such a webservice using HTTP-BINDING as simple as SOAP Binding? 2)Could I write a service and publish it with a WSDL use HTTP-Binding as simple as SOAP Binding? Thanks any suggestion.

Does CXF support Webservice Http binding?

Hi: Axis2 .net could publish a PortType with Http-Binding in WSDL. That's to say: when user write a service business logical, the user could choose to publish the service interface to be a Soap-Binding Webservice or a Http-Binding Webservice without changed the definition of java /.net

Exception(Unexpected end of file from server) of CXF

Recently I always encounter a Unexpected end of file from server Exception at CXF client side. it seems this exception is caused by the CXF Serverside has unexcepted release the http connection ; I tried some effort to to use a simple test case to regenerate such a exception; Following is a