Re: CXF logging

John-M Baker wrote: Wouldn't it make sense to use commons logging? I implemented it on some code recently and it seems a bit of a no brainer... John Baker No, commons logging is broken by design. Apache Jakarta should really deprecate it. It has classloader issues (and memory leaks) tha

Re: JSON output format problem

You need to set the content-type on the endpoint, not on the service factory bean: e.g. http://apache.org/cxf/binding/http";> class="org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean"> gdprao wrote: Hi, I am trying CXF JSON web service. I

Re: Automatic Testing CXF Web Services out of the box

It depends what you're trying to test: the network interface, or the service API. There's no need to create (or use) the network interface if what you actually want to test is the service API. Vincenzo Vitale wrote: Hi, I would like to automatic testing my web services out of the box, that i

Re: NameSpaceHandling error

"C:\Apps\apache-cxf-2.0.1-incubator\lib\cxf-2.0.1-incubator.ja r" this path in front of my classpath. Rest all the jars from CXF library distribution has been copied over to WEB-INF/lib. I did follow the tutorial and that's how I have configured my project. Sushil -

Re: NameSpaceHandling error

From the Java documentation for "NoClassDefFoundException": "The searched-for class definition existed when the currently executing class was compiled, but the definition can no longer be found." Looks like you're missing a Jar file. Please make sure you're including all the Jars referenced h

Re: AW: cxf-2.0.1-incubator - dependency incompatibility with hibernate

You can use the element when referencing the CXF jars to remove the incompatible ASM import. Holger Stolzenberg wrote: The problem refers to version 2.0.1-INCUBATOR. Regarding the POM at http://people.apache.org/repo/m2-incubating-repository/org/apache/cxf/cxf-rt-frontend-jaxws/2.0.1-incubato

Re: JSON output

The spring configuration will look something like this: http://apache.org/cxf/binding/http";> class="org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean">

HTTP Authentication

Any suggestions on how I might approach triggering HTTP authentication when a specific exception is thrown from a service using the HTTP binding? If I could simply let the exception propogate to the servlet container (without being turned into an XML fault message) then that would be best for

Re: Eclipse XSD validation for jaxws.xsd

I ended up just unpacking the JARs and pointing eclipse to the actual XSD files. You'll also need to set the key type to 'Schema Location'. blacksheep wrote: Durga, Were you able to figure out the problem ? Looks like I have the same problem. Thanks, Mustafa gdprao wrote: Thanks for

Re: AJAX -> [JSON] -> REST service

I think you also need to associate some meta-data with the id parameter in your method signature since Java doesn't maintain any information about parameter names. You can do this with the @WebParam annotation, e.g. @Get @HttpResource(location="/employees/{id}") Employee getEmployee(@WebParam(

Re: Weird character encoding problem

Are you specifying an encoding when you compile your Java classes? i.e. javac -encoding utf8 MyClass.java? Oliver Flasch wrote: Hi, I'm using a "wsdl2java"-generated CXF Client to talk to a .NET Webservice. When sending a string containing some special characters (german "umlaute" in my case

Re: WSS4J implementation in CXF

No, this won't work. I posted an e-mail on the dev list about this yesterday. The problem is the WSS4JInInterceptor doesn't accept a Map only a Map so there is no way to ref an instantiated object. Julio Arias wrote: Hello - You could use something like this, but there is a bug in the WSS

Configuring a JSON endpoint via Spring

I've been trying to add a JSON endpoint to my service by updating the Spring configuration but with no success. The REST based version works just fine, but the JSON version either: returns an empty-page for the Mapped version or returns: {"ns1:XMLFault":{"@xmlns":{"ns1":"http:\/\/cxf.apache.