RE: Getting started with JAX-WS

2007-01-18 Thread Liu, Jervis
Hi Cameron, the hello_world samples are located under trunk\distribution\src\main\release\samples or cxf-installation-dir\cxf-2.0-incubator-RC-SNAPSHOT\samples in your cxf distribution. Cheers, Jervis From: Cameron Taggart [mailto:[EMAIL PROTECTED] Sent: Thu

RE: Programatically installing interceptors per (Bus|Service|Endpoint)

2007-03-20 Thread Liu, Jervis
Hi Fred, Not sure if I understand your question correctly. If what you want is to instantiate and install interceptors per service/endpoint/binding, for example, you may have a strategy that can load different interceptors depending on a specific binding property, yes surely you can do this.

wsdlLocation removed from demo's impl code?

2007-04-23 Thread Liu, Jervis
Hi, I am currently looking into CXF-584 (hello_world sample (Running demo with HTTP Get section) doesn't work), the cause of this problem is because wsdlLocation attribute was removed from server's impl code (take a look into GreeterImpl.java). We now load server side service module from class

RE: Problem matching URI templates with RESTful binding

2007-05-31 Thread Liu, Jervis
Hi Adrian, we also have a similar system test under org.apache.cxf.systest.rest.RestClientServerBookTest. If you don't mind playing around with CXF source code, you can modify this test case to reproduce the problem you reported and submit the modified test case as a patch. Cheers, Jervis

RE: Skipping some layers in the interceptor chain

2007-06-05 Thread Liu, Jervis
: +44 (0) 1372 756407 Fax: +44 (0) 1372 740055 Mob: 07740 817586 E-mail: [EMAIL PROTECTED] www.atkinsglobal.com/its -Original Message- From: Liu, Jervis [mailto:[EMAIL PROTECTED] Sent: 04 June 2007 03:20 To: cxf-user@incubator.apache.org Subject: RE: Skipping

RE: DynamicClientFactory skipping some layers

2007-06-06 Thread Liu, Jervis
So you've got it. :-) Regarding whether or not dispatch provider goes through the binding layer, please see more comment in-line below. Cheers, Jervis -Original Message- From: Shaw, Richard A [mailto:[EMAIL PROTECTED] Sent: 2007?6?6? 17:08 To: cxf-user@incubator.apache.org Subject:

RE: problem invoking on JAX-WS provider

2007-06-13 Thread Liu, Jervis
Hi Conrad, I've fixed the NoSuchElementException, but not sure if this fixed your service as well. If your service still does not work, would you be able to provide a simplified test case so that we can reproduce the problem you are having? Thanks. Cheers, Jervis -Original Message-

RE: sending POST with emtpy body to RESTFUL server causes error

2007-07-03 Thread Liu, Jervis
In general, yes, any non-idempotent operations should not be required to have a body. But when it comes to using JAX-WS Dispatch/Provider to implement a Restful service, its really down to the semantics of Provider/Dispatch per spec. As the spec is not specific on this point, we could extend

RE: Exposing methods

2007-07-12 Thread Liu, Jervis
Hi Julio, if exclude=true did work, this proved that your endpointInterface class didnt get loaded by CXF. The logic behind the scene is that CXF will try to load endpointInterface class using @WebService(endpointInterface =) annotation, if it successfully gets the interface loaded, only

RE: Exposing methods

2007-07-13 Thread Liu, Jervis
Hi, I actually believe this is a bug in CXF. What happened in CXF is that we first reflect impl class, all methods defined in impl class become potential candidates for publishing. Then we check interface, if the method under consideration does not exist in the interface, we will fall back to

RE: Need to eliminate use of SOAP for Http-REST

2007-07-15 Thread Liu, Jervis
Hi Brad, Currently there are two ways to build RESTful service with CXF, using CXF HTTP binding or using JAX-WS Dispatch/Provider API. JAX-WS Dispatch/Provider approach is just using JAX-WS API, so it is SOAP/HTTP based (but you can also configure it to use XML binding instead). CXF HTTP

RE: Need to eliminate use of SOAP for Http-REST

2007-07-15 Thread Liu, Jervis
-REST Jervis, Thanks for the reply. An update on the situation -- there is (was) a bug here, which Dan Diephouse is addressing. He found me a workaround to my problem for now. Brad Liu, Jervis wrote: Hi Brad, Currently there are two ways to build RESTful service with CXF, using CXF HTTP

RE: Adobe FLex 2 JSON client: problem with parameter order

2007-07-16 Thread Liu, Jervis
Hi Luca, the parameter orders on the client side should not matter. The server retrieves input using name/value pairs. Having this said, I cant guarantee you that it is bug-free. ;-) I just added a REST system test using JSON as content type

RE: attempting HelloWorld service, getting NULL return value

2007-07-17 Thread Liu, Jervis
Hi Marty, as you said, you've examined the message flowing between client and client and it is correct, in this case, must be sth wrong with your client. You may want to send us your client code, so that we can take a quick look to see what happened there. Thanks, Jervis -Original

RE: Using Local Transport for JUnit Tests

2007-07-17 Thread Liu, Jervis
Hi Chris, to use local transport, you need to manually register LocalTransportFactory with all the namespaces that might be used, for example, http://schemas.xmlsoap.org/soap/http;. An example of how this is done can be found from

RE: POSTing customer using REST

2007-07-24 Thread Liu, Jervis
Hi Mansour, do you have targetNamespace attribute defined in your WebService annotation, such as @WebService(targetNamespace = http://book.acme.com;)? This targetNamespace is needed for marshal/unmarshal between input and your Customer object. There were similar problem reported in the mailing

RE: YOKO CXF CORBA Web Service using ProviderCorbaMessage

2007-07-30 Thread Liu, Jervis
Coming to think of this again, I found supporting ProviderCorbaMessage isn't that difficult as I originally thought. We have some manual checks of binding type in DispatchInDatabindingInterceptor\DispatchOutDatabindingInterceptor, such as if (binding == soapbinding) then blabla. Actually we

RE: http rest sample does not compile

2007-07-30 Thread Liu, Jervis
Thanks for the report. Fixed. Cheers, Jervis -Original Message- From: Mansour Raad [mailto:[EMAIL PROTECTED] Sent: 2007?7?30? 18:24 To: cxf-user@incubator.apache.org Subject: http rest sample does not compile svn up the latest. cd [install]/samples/restful_http_binding ant server I get

RE: Plain Old Xml over Http

2007-07-30 Thread Liu, Jervis
Hi Ray, What do you mean by not do the auto-magical xml stuff that CXF seems to support now in the REST support? Do you mean you want to access the raw xml message payload instead of marshalling the xml into objects? If this is the case, you probably want to use the JAX-WS Provider/Dispatch

RE: YOKO CXF CORBA Web Service using ProviderCorbaMessage

2007-08-02 Thread Liu, Jervis
19:52 To: cxf-user@incubator.apache.org; Liu, Jervis Subject: RE: YOKO CXF CORBA Web Service using ProviderCorbaMessage Hi Jervis, it really sounds great, cxf would be more flexible then. Thank you for your replies. So do you plan adding support of that to cxf? And would it be possible to know

RE: YOKO CXF CORBA Web Service using ProviderCorbaMessage

2007-08-02 Thread Liu, Jervis
/30, Liu, Jervis [EMAIL PROTECTED]: Hi Michal, The short answer is we do not support ProviderCorbaMessage right now in CXF, I will discuss into details why we can not support ProviderCorbaMessage with standard JAX-WS APIs in a following email. You mentioned CORBA binding is working for you

RE: Good way to return a RowSet from a service?

2007-08-02 Thread Liu, Jervis
It looks like you are trying to do some kind of Database Web services. I am afraid in the world of Database web services, you would never want to return RowSet directly because RowSet object is too complex/big to be mapped to XML, not to mention other concerns like performance etc. Many

RE: YOKO CXF CORBA Web Service using ProviderCorbaMessage

2007-08-03 Thread Liu, Jervis
it to Yoko CORBA binding along with WSDL file to make a dynamic call. It seems to me the terms corba cxf binding and dynamic cannot live together... Best regards, Lukas 2007/8/2, Liu, Jervis [EMAIL PROTECTED]: Hi, have a new question. I suppose the reason why you want to use Provider interface

RE: YOKO CXF CORBA Web Service using ProviderCorbaMessage

2007-08-04 Thread Liu, Jervis
regards, Lukas 2007/8/2, Liu, Jervis [EMAIL PROTECTED]: Hi, have a new question. I suppose the reason why you want to use Provider interface for CORBA binding is that you want to access raw CORBA message payload so that you can parse operation info and input parameters by yourself

RE: JAX-WS MessageContext properties

2007-08-11 Thread Liu, Jervis
The support for WSDL_DESCRIPTION etc was added into CXF after 2.0 release. Try CXF2.0.1 instead. Cheers, Jervis -Original Message- From: Bokde, Dhiraj [mailto:[EMAIL PROTECTED] Sent: 2007年8月11日 3:07 To: cxf-user@incubator.apache.org Subject: JAX-WS MessageContext properties

RE: JRAStrategry work incorrectly?

2007-08-12 Thread Liu, Jervis
Kevin, internally CXF follows JAX-WS spec to process annotations. JAX-WS section 3.3, if the WebService annotation on the class under consideration has a endpointInterface element, then the interface referred by this element is for all purposes the SEI associated with the class.. I.e., if you

RE: JRAStrategry work incorrectly?

2007-08-12 Thread Liu, Jervis
Message- From: Liu, Jervis [mailto:[EMAIL PROTECTED] Sent: 2007?8?13? 11:04 To: cxf-user@incubator.apache.org Subject: RE: JRAStrategry work incorrectly? Kevin, internally CXF follows JAX-WS spec to process annotations. JAX-WS section 3.3, if the WebService annotation on the class under

RE: returning xml from REST based web service

2007-08-13 Thread Liu, Jervis
Hi Dave, please note your XML snippet that is defined as XSD:string will always be encoded no matter with JAXB binding or Aegis binding. A string within an XML document has to be encoded. One workaround is to redesign your schema, give your xml snippet a concrete schema type instead of

RE: AJAX - [JSON] - REST service

2007-08-16 Thread Liu, Jervis
You have to set your REST service to unwrapped mode if you want URL template /employees/{id} maps to a simple type long id. Otherwise CXF HTTP binding will marshal the request (the URL in the case of HTTP GET) into a wrapper class GetEmployee. Cheers, Jervis -Original Message- From:

RE: Unable to create message factory for SOAP

2007-08-16 Thread Liu, Jervis
Not familiar with JBOSS, look likes JBOSS has its own SAAJ impl, and the exception was caused by initializing the MessageFactory. I suggest you try following code in your JBOSS env to see what happens: MessageFactory factory = MessageFactory.newInstance(); Cheers, Jervis

RE: Unable to create message factory for SOAP

2007-08-17 Thread Liu, Jervis
to quite cut it either. 2007/8/17, Liu, Jervis [EMAIL PROTECTED]: Not familiar with JBOSS, look likes JBOSS has its own SAAJ impl, and the exception was caused by initializing the MessageFactory. I suggest you try following code in your JBOSS env to see what happens

RE: DataBinding problems (Timestamp and HashMap) using JAXB

2007-08-17 Thread Liu, Jervis
Neither java.sql.Timestamp nor HashMap are supported by JAXB. A common practice is abstracting data from unsupported types to a supported JAVA types or to user defined POJOs. For example, Timestamp can be represented as a String, and if you know HashMap is used as HashMapInteger, String, you

RE: AJAX - [JSON] - REST service

2007-08-19 Thread Liu, Jervis
Sorry, it is my bad. What I really meant to say is: You have to set your REST service to WRAPPED mode if you want URL template /employees/{id} maps to a simple type long id. In the UNWRAPPED mode CXF HTTP binding marshals the request (the URL in the case of HTTP GET) into a wrapper class, i.e.,

RE: Generic ProviderDOMSource server and WSDL metadata

2007-08-19 Thread Liu, Jervis
Hi Dhiraj, it looks like sth wrong in your WSDL, most likely the service name defined in your WSDL does not match with the service name specificed in your spring cfg file. BTW, I don't really get the reason why you want to access to the WSDL metadata like wsdlLocation, serviceName, portName,

RE: Generic ProviderDOMSource server and WSDL metadata

2007-08-22 Thread Liu, Jervis
: Liu, Jervis [mailto:[EMAIL PROTECTED] Sent: Sunday, August 19, 2007 8:35 PM To: cxf-user@incubator.apache.org Subject: RE: Generic ProviderDOMSource server and WSDL metadata Hi Dhiraj, it looks like sth wrong in your WSDL, most likely the service name defined in your WSDL does not match

RE: JSON output

2007-08-22 Thread Liu, Jervis
Hi Kaleb, I am really not sure if it makes sense to convert SOAP message to JSON. But if the payload is Plain-old--XML(POX), it should be doable in CXF. At the moment, CXF HTTP binding can serve RESTful service in both POX and JSON payload. Details can be found from

RE: Restful Service client exception

2007-08-22 Thread Liu, Jervis
Could you please paste out your com.fm.services.ServiceImpl and com.fm.services.IService code? I noticed that client.doService(foo) returns a ListImage. Not sure what your code looks like, but this might be the place where the problem comes from. Cheers, Jervis -Original Message-

RE: Restful Service client exception

2007-08-23 Thread Liu, Jervis
returns the correct values though. Thanks Sriram Liu, Jervis wrote: Could you please paste out your com.fm.services.ServiceImpl and com.fm.services.IService code? I noticed that client.doService(foo) returns a ListImage. Not sure what your code looks like, but this might

RE: Restful Service client exception

2007-08-28 Thread Liu, Jervis
Liu, Jervis wrote: Ok, I see the problem. Your service is using wrapped mode, unfortunately URIMapper did not handle Wrapped/Unwrapped operation correctly. I have filed JIRA cxf-938 for this. Thanks, Jervis -Original Message- From: Sric [mailto:[EMAIL PROTECTED

RE: Bus Features [was: Logging ...]

2007-08-29 Thread Liu, Jervis
Hi Fred, I recalled we had a similar discussion before. In your code snippet below, the logging interceptors will be installed twice. I wont say cxf:bus is a root scope configuration as there is no hierarchy relationships among bus, endpoints and bindings. Bus, endpoints and bindings are just

RE: Obtaining source address and operation name

2007-08-30 Thread Liu, Jervis
Hi What code did you use to retrieve WSDL_OPERATION, WSDL_PORT etc? Thanks, Jervis -Original Message- From: James Royalty [mailto:[EMAIL PROTECTED] Sent: 2007?8?31? 8:28 To: cxf-user@incubator.apache.org Subject: Obtaining source address and operation name Hi, I'm trying to

RE: Obtaining source address and operation name

2007-08-30 Thread Liu, Jervis
null. The services are using a servlet transport, btw. Thanks! -- James Liu, Jervis wrote: Hi What code did you use to retrieve WSDL_OPERATION, WSDL_PORT etc? Thanks, Jervis -Original Message- From: James Royalty [mailto:[EMAIL PROTECTED] Sent: 2007?8?31? 8

RE: Obtaining source address and operation name

2007-09-03 Thread Liu, Jervis
?9?1? 0:09 To: cxf-user@incubator.apache.org Cc: Liu, Jervis Subject: Re: Obtaining source address and operation name Jervis, Those properties are on the message, not the exchange. I just checked both the DocLitInInterceptor and RPCInInterceptor and they put them on the message

RE: Memory leak in client?

2007-09-04 Thread Liu, Jervis
Hi Joe, based on the information you supplied, I wont necessarily say there is a memory leak. Internally CXF runtime maintains a service model which is built either from WSDL or from POJO, both on the client side and server side. And this service model will keep alive until the server or client

RE: Memory leak in client?

2007-09-05 Thread Liu, Jervis
run this, and you see the memory usage increased steadily after 1000 loops, then its definitely a memory leak. Jervis --Joe On Sep 4, 2007, at 10:10 PM, Liu, Jervis wrote: Hi Joe, based on the information you supplied, I wont necessarily say there is a memory leak. Internally CXF

RE: Elements and parts seem to default to return - which upsets WSDL2X as return is generally a reserved word

2007-09-10 Thread Liu, Jervis
Jon, the mapping name of return is per JAX-WS 2.0 spec. Section 3.6.1: Conformance (Result naming): The javax.jws.WebResult annotation (see 7.10.4) MAY be used to specify the name of the wsdl:part or XML Schema element declaration corresponding to the Java method return type. If both the

RE: Not able to catch desired Fault type

2007-09-13 Thread Liu, Jervis
Your WSDL snippet and the response message look ok. You may want to send out your WSDL file and client/server code (or paste them in a JIRA), so that we can have a quick debug to see whats going wrong there. Thanks, Jervis -Original Message- From: Richard Mixon [mailto:[EMAIL

RE: Wsdl Versioning

2007-09-13 Thread Liu, Jervis
Hi Dave, we've had a very basic versioning implementation. Basically how it works is an interceptor sitting at the beginning of in-bound interceptor chain as a mediator to inspect then dispatch the coming request to different endpoints. An example can be found from a system test sample:

RE: Wsdl Versioning

2007-09-15 Thread Liu, Jervis
? On 9/14/07, Jean-François Daune [EMAIL PROTECTED] wrote: This document is quite interesting about this subject: http://blogs.iona.com/sos/20070410-WSDL-Versioning-Best-Practise.pdf Cheers, J-F -Message d'origine- De : Liu, Jervis [mailto:[EMAIL PROTECTED] Envoyé

RE: Wsdl Versioning

2007-09-17 Thread Liu, Jervis
@incubator.apache.org Subject: Re: Wsdl Versioning It looks like I might not be able to set this up through cxf.xml? I don't see a way to get the MultipleEndpointObserver from the JaxWsServiceFactoryBean so that I can add a routingInterceptor to it. On 9/15/07, Liu, Jervis [EMAIL PROTECTED

RE: Wsdl Versioning

2007-09-18 Thread Liu, Jervis
) { InputStream is = message.getContent(InputStream.class); System.out.println (Message + message); System.out.println(EndpointSet + eps); } } On 9/17/07, Liu, Jervis [EMAIL PROTECTED] wrote: Hi Dave, Firstly you need to make sure you are using SOAP binding

RE: JAX-WS Handlers conflict with JBoss client?

2007-09-23 Thread Liu, Jervis
Hi you need to set messageFactory like this: java.lang.System.setProperty(javax.xml.soap.MessageFactory,com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl); Also see this discussion: http://www.nabble.com/Unable-to-create-message-factory-for-SOAP-tf4280273.html#a12196539 Cheers,

RE: Message level service

2007-10-11 Thread Liu, Jervis
JAX-WS Dispatch/Provider API should give you what you want. There is a sample named jaxws_dispatch_provider in CXF distribution demonstrates how to write dispatch/provider in CXF. The reason why you got that exception is because you are using CXF HTTP binding in your configuration, which is the

RE: Serialization of XML attributes to Java Types

2007-10-24 Thread Liu, Jervis
CXF HTTP REST binding uses JAXB data binding as the underlying marshal/unmarshal mechanism. I have not tried this by myself, but your case should be a matter of tuning JAXB to do a customized mapping for you. For example, if you want to map MyObject myVar1=value 1 myVar2=value 2 / to MyObject

RE: Unintended Consequences...

2007-10-24 Thread Liu, Jervis
This indeed looks like a bug to me. I vaguely recalled that I once ran into a weird problem with SAAJ impl, which is that in some cases SOAPBody() wont be not properly initialized until SOAPMessage.writeTo() or some other similar methods are called. I guess what might happen is that CXF creates

RE: empty response object

2007-10-28 Thread Liu, Jervis
Looks like you need to post a complete test case (at least the WSDL file and client side code) in order to fully understand what the problem is. Thanks, Jervis -Original Message- From: tirtza [mailto:[EMAIL PROTECTED] Sent: 2007?10?29? 3:24 To: cxf-user@incubator.apache.org

RE: Client returns empty string!

2007-10-31 Thread Liu, Jervis
Hi, using JAX-WS Dispatch APIs should be easier than using SAAJ directly. Actually, the problem you ran into has been discussed in thread [1] [2]. Note, if you use Dispatch, make sure you set the mode to MESSAGE. In this case it is very similar to using SAAJ directly, once you get back the

RE: Gzip encoding

2007-11-04 Thread Liu, Jervis
Hi Shaw, you can configure your client side interceptors using feature. An example can be found from dispatch system test: \trunk\systests\src\test\java\org\apache\cxf\systest\dispatch\TestDispatchFeature.java and client-config.xml. Cheers, Jervis -Original Message- From: Daniel

RE: ClientFactoryBean AbstractMethodError

2007-11-04 Thread Liu, Jervis
I probabaly should remove JAX-WS style client codes from restful_http_binding demo, as it constantly causes confusions. In theory, JAX-WS style client APIs should work with RESTful services that published using CXF HTTP binding, as this is symmetric to what the server side has to do to

RE: ClientFactoryBean AbstractMethodError

2007-11-05 Thread Liu, Jervis
().setWrapped(true); return sf.create(); } This is almost exactly the same as the server code from the demo - the code that works. However, in my example I receive the stack trace from above on the sf.create() method. On 11/4/07, Liu, Jervis [EMAIL PROTECTED

RE: Programmatically publishing a REST endpoint

2007-11-07 Thread Liu, Jervis
Currently there are three ways to build a RESTful service in CXF. [1] and [2] should give you enough information on how to use CXF HTTP binding and JAX-WS Dispatch/Provider to build a RESTful service. Now we have a third option - using JSR-311. You are very welcome to try this new feature out,

RE: Programmatically publishing a REST endpoint

2007-11-08 Thread Liu, Jervis
-Original Message- From: Liu, Jervis [mailto:[EMAIL PROTECTED] Sent: 2007?11?8? 15:06 To: cxf-user@incubator.apache.org Subject: RE: Programmatically publishing a REST endpoint Currently there are three ways to build a RESTful service in CXF. [1] and [2] should give you enough

RE: Programmatically publishing a REST endpoint

2007-11-11 Thread Liu, Jervis
-Original Message- From: Tom Davies [mailto:[EMAIL PROTECTED] Sent: 2007?11?12? 6:23 To: cxf-user@incubator.apache.org Subject: Re: Programmatically publishing a REST endpoint On 08/11/2007, at 7:37 PM, Liu, Jervis wrote: Here you go, a brief document on how to build

RE: when are interceptor chains created?

2007-11-13 Thread Liu, Jervis
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

RE: when are interceptor chains created?

2007-11-13 Thread Liu, Jervis
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 chains

RE: Access to SOAPMessage object within the service implementation class

2007-11-18 Thread Liu, Jervis
Hi, You won't be able to access SOAPMessage unless you use JAX-WS provider as your service implementation. Another way to get around this is using SOAP handlers, you can simply return false in your soap handler. Let's say you return false in your soap handler in the inbound direction, in this

RE: Interceptors pulling values out of requests

2007-11-19 Thread Liu, Jervis
I just updated the wiki page [1], hopefully it is more clear now how to write and configure user interceptors. Please let me know if there is anything missing or still not clear on this page. I am not sure what type of parameters you want to access through interceptors, lets presume you want to

RE: Interceptors pulling values out of requests

2007-11-20 Thread Liu, Jervis
To: cxf-user@incubator.apache.org; Liu, Jervis Subject: RE: Interceptors pulling values out of requests Thank you for the information. It isn't quite solving my issue though. What I am trying to do is to log the values in my request stream. My request looks like this: ?xml version

RE: Interceptors pulling values out of requests

2007-11-22 Thread Liu, Jervis
method to dispatch to based on different criteria (eg, RPC or Doc lit wrapped or REST HTTP binding..). Cheers, Jervis -Original Message- From: Vespa, Anthony J [mailto:[EMAIL PROTECTED] Sent: 2007年11月21日 22:19 To: Liu, Jervis; cxf-user@incubator.apache.org Subject: RE: Interceptors

RE: How to get wsdl for java_first_jaxws on Tomcat

2007-11-22 Thread Liu, Jervis
All CXF demos can be deployed into a Servlet container. Please refer to samples directory README for building demos in a servlet container. Cheers, Jervis -Original Message- From: Bruce Z [mailto:[EMAIL PROTECTED] Sent: 2007年11月23日 1:01 To: cxf-user@incubator.apache.org Subject:

RE: what would be the best place to introduce xslt transformer for response message

2007-11-25 Thread Liu, Jervis
I presume you are using SOAP binding. The best place to look at is the SAAJOutInterceptor . What this interceptor does is very similar to what you want to achieve. SAAJOutInterceptor firstly replaces the output stream that writes the output to socket with its own output stream that writes

RE: Throwing faults from within an Interceptor

2007-11-26 Thread Liu, Jervis
Hi, it is possible to throw a checked Exception from CXF interceptors. Make sure the exception thrown from your interceptor is declared as an exception on the operation being invoked, otherwise this exception will not be recognized as a checked Exception. Also was the MyFault class generated by

RE: Throwing faults from within an Interceptor

2007-11-26 Thread Liu, Jervis
what interceptors you have in your fault out chain. Thanks, Jervis 2007/11/26, Liu, Jervis [EMAIL PROTECTED]: Hi, it is possible to throw a checked Exception from CXF interceptors. Make sure the exception thrown from your interceptor is declared as an exception on the operation being

RE: what would be the best place to introduce xslt transformer for response message

2007-11-26 Thread Liu, Jervis
Here you go. It looks like below (roughly): import java.io.IOException; import java.io.OutputStream; import javax.xml.transform.Transformer; import javax.xml.transform.stream.StreamResult; import javax.xml.transform.stream.StreamSource; import org.apache.cxf.binding.soap.SoapMessage; import

RE: Throwing faults from within an Interceptor

2007-11-27 Thread Liu, Jervis
http request on thread: Thread[http-127.0.0.1-8080-1,5,jboss] 2007/11/27, Liu, Jervis [EMAIL PROTECTED]: -Original Message- From: Christian Vest Hansen [mailto:[EMAIL PROTECTED] Sent: 2007年11月26日 18:36 To: cxf-user@incubator.apache.org Subject: Re: Throwing faults

RE: Custom Fault in Interceptor

2007-11-27 Thread Liu, Jervis
See this email thread: http://www.nabble.com/Throwing-faults-from-within-an-Interceptor-tf4860623.html -Original Message- From: Mustafa Egilmezbilek [mailto:[EMAIL PROTECTED] Sent: 2007年11月27日 17:20 To: cxf-user@incubator.apache.org Subject: Custom Fault in Interceptor Hello,

RE: differences between Interceptors and Handlers

2007-11-27 Thread Liu, Jervis
CXF interceptor API is the core of CXF runtime to process message flows, internally JAX-WS handlers are implemented as CXF interceptors. If you want to stick to the spec, you would avoid using CXF interceptors directly if possible. However there are circumstances that CXF interceptors give you

RE: Empty string namespace mapping with JSON and HTTP Post

2007-11-27 Thread Liu, Jervis
-Original Message- From: mgibble [mailto:[EMAIL PROTECTED] Sent: 2007年11月28日 4:29 To: cxf-user@incubator.apache.org Subject: Empty string namespace mapping with JSON and HTTP Post I am using the restful_http_binding sample and I have changed the following lines: //

RE: restful_jaxrs sample

2007-11-28 Thread Liu, Jervis
-Original Message- From: Eric Le Goff [mailto:[EMAIL PROTECTED] Sent: 2007年11月28日 17:26 To: cxf-user@incubator.apache.org Subject: restful_jaxrs sample I was trying to understand to jaxrs frontend provided by CXF and the restful_jaxrs demo helped a lot. Then I tried to write

RE: restful_jaxrs sample

2007-11-28 Thread Liu, Jervis
-Original Message- From: Eric Le Goff [mailto:[EMAIL PROTECTED] Sent: 2007年11月28日 20:31 To: cxf-user@incubator.apache.org Subject: Re: restful_jaxrs sample On Nov 28, 2007 10:53 AM, Liu, Jervis [EMAIL PROTECTED] wrote: I believe this is because you don't have following lines

RE: restful_jaxrs sample

2007-11-29 Thread Liu, Jervis
{ ... } -Original Message- From: Liu, Jervis [mailto:[EMAIL PROTECTED] Sent: 2007年11月29日 11:48 To: cxf-user@incubator.apache.org Subject: RE: restful_jaxrs sample -Original Message- From: Eric Le Goff [mailto:[EMAIL PROTECTED] Sent: 2007年11月28日 20:31 To: cxf-user

RE: Cxf Issue

2007-12-05 Thread Liu, Jervis
Hi can you be more specific about the problem please? Some code snippets of your service implementation and configuration that can help us to reproduce the problem or a complete test case would be helpful. Cheers, Jervis -Original Message- From: priya j [mailto:[EMAIL PROTECTED]

RE: Cxf Issue

2007-12-05 Thread Liu, Jervis
the FrontEndService is another class, if it is an interface the execution fails in client side. Can you suggest me how to proceed. [Liu, Jervis] If I understand your problem correctly, your service fails to return a valid result (does the String webService (String queryString) method throw an exception

RE: jaxws_dispatch_provider demo

2007-12-09 Thread Liu, Jervis
Hi Eric, it looks like your client did not sent out an valid request to the server. A quick way to verify this is using sth like tcpmon to sniff the message you send on wire. In your client code, did you change the service and port QName to reflect your own namespaces? I.e., following lines:

RE: Configuring JAX-WS Handler in spring configuration file

2007-12-10 Thread Liu, Jervis
There is a standard way to configure JAX-WS handlers using configuration files, please refer to the jaxws_handlers demo (jaxws_handlers\src\demo\handlers\common\demo_handlers.xml) shipped with CXF distribution. The lifecycle of JAX-WS handlers has to be handled by JAX-WS runtime, not by

RE: Can't route REST calls to methods using CXF2.0.3 and JBoss

2007-12-10 Thread Liu, Jervis
Cannot spot any obvious error in your code. Could you copy me the log messages when your server starts up, it should look like sth below: 2007-12-11 11:49:25 org.apache.cxf.service.factory.ReflectionServiceFactoryBean buildServiceFromClass INFO: Creating Service

RE: Configuring JAX-WS Handler in spring configuration file

2007-12-11 Thread Liu, Jervis
-Original Message- From: Liu, Jervis [mailto:[EMAIL PROTECTED] Sent: 2007年12月11日 10:48 To: cxf-user@incubator.apache.org Subject: RE: Configuring JAX-WS Handler in spring configuration file There is a standard way to configure JAX-WS handlers using configuration files, please

RE: sample failure: restfull_http_binding

2007-12-16 Thread Liu, Jervis
For your information, CXF-889 has been fixed in CXF2.0.3, though the Get Customers! button is still not working with IE (works with Firefox). I created https://issues.apache.org/jira/browse/CXF-1306 to track this. Cheers, Jervis -Original Message- From: Daniel Kulp [mailto:[EMAIL

RE: wrapped mode false fails in IriDecoderHelper

2007-12-16 Thread Liu, Jervis
This looks like a bug. Could you create a jira for this with a complete test case please. At the same time, I would recommend you to give CXF JSR-311 (JAX-RS) implementation a try, it has similar functionalities as CXF HTTP binding provides, but it is more standard based. CXF JAX-RS currently

RE: sample failure: restfull_http_binding

2007-12-17 Thread Liu, Jervis
Liu, Jervis wrote: For your information, CXF-889 has been fixed in CXF2.0.3, though the Get Customers! button is still not working with IE (works with Firefox). I created https://issues.apache.org/jira/browse/CXF-1306 to track this. Cheers, Jervis -Original Message

RE: Queries in handling the exeception for Http binding for RESTful Service

2007-12-17 Thread Liu, Jervis
is that any way i can remove the ns1 and faultstring from my output. So that the following output is ErrorDetails xmlns=http://sfe.sphsearch.sg; messageInvalid request parameter query./message /ErrorDetails [Liu, Jervis] You got the output above probably because you throw

RE: extending databinding

2007-12-18 Thread Liu, Jervis
Hi Mariano, what kind of data bindings are you looking for? Is it sth very simple such as marshaling an Inputstream to a Source object (in this case, you want look into SourceDataBinding.java) or sth a little bit more complex based on schemas, such as JAXB databinding or Aegis databinding. In

RE: JAXB Unmarshalling

2007-12-19 Thread Liu, Jervis
/archive/2006/03/restful_web_ser_1. html [Liu, Jervis] You don’t have to use JAX-WS Dispatch API in this case. Once you grab the InputStream from HTTPClient (or other lightweight http client stack), you can call JAXB to marshal the response to your Customer object. There is no point to use a heavy

RE: JAXB Unmarshalling

2007-12-20 Thread Liu, Jervis
that there might not be much point in dealing directly with JAXBContext and pretend that your code is so light and free :-) Cheers, Sergey - Original Message - From: Liu, Jervis [EMAIL PROTECTED] To: cxf-user@incubator.apache.org Sent: Thursday, December 20, 2007 7:18 AM Subject: RE: JAXB

RE: CXF and JSON

2007-12-20 Thread Liu, Jervis
I would encourage you to try CXF JSR-311 (JAX-RS) implementation instead. It is standard based (CXF HTTP binding is not standard based), and the development activities around CXF JSR-311 are much more active. CXF JSR-311 (JAX-RS) demo: samples\restful_jaxrs System test:

RE: Rest Header Info

2008-01-08 Thread Liu, Jervis
Are you using CXF HTTP Binding to build your REST service, or CXF JAX-RS (JSR-311) instead? In CXF JAX-RS (JSR-311), the standard way to access HTTP headers is using @HeaderParam, like below: @HttpMethod(GET) @UriTemplate(/books/{bookId}/) public Book getBook(@UriParam(bookId)

RE: using multiple values for @ProduceMime

2008-01-08 Thread Liu, Jervis
Hi Akos, you definitely should be able to set multiple values for @ProduceMime. According to spec, if @ProduceMime contains multiple MIME types (or it’s a wild card such as */*), the actual output content type being used is determined by: 1. the output Java type: i.e., if your method is

RE: GZIP compression done properly

2008-01-08 Thread Liu, Jervis
Hi Ian, this contribution is very welcome. So your change is based on the existing configuration_interceptor demo, right? Please file a jira with your code as attachment, that should be enough. Thanks. Cheers, Jervis -Original Message- From: ianroberts [mailto:[EMAIL PROTECTED]

RE: Rest Header Info

2008-01-08 Thread Liu, Jervis
be passed through the URL. So that'll be ugly. Arg. On Jan 8, 2008 3:21 AM, Liu, Jervis [EMAIL PROTECTED] wrote: Are you using CXF HTTP Binding to build your REST service, or CXF JAX-RS (JSR-311) instead? In CXF JAX-RS (JSR-311), the standard way to access HTTP headers is using @HeaderParam

RE: Handlers and Client target - How do I do that in cxf

2008-01-10 Thread Liu, Jervis
is the cxf equivalent? [Liu, Jervis] CXF supports the standard way per JAX-WS spec to configure handler chain on the server side. An example of this can be found in samples\jaxws_handlers in CXF distribution.. client side, I 1 programatically create a list of Handlers ( the same logging Handler

  1   2   >