What I had to do is to wrap jaxb:globalBindings with another jaxb:bindings. <jaxb:bindings version=”2.0″ xmlns:jaxb=”http://java.sun.com/xml/ns/jaxb”> <jaxb:bindings> <jaxb:globalBindings generateElementProperty=”false”/> </jaxb:bindings> </jaxb:bindings> Now everything is working, there is no JAXBElement<String> generated anymore.
If you use Jackson (a great JSON lib – kind of the standard for Java I believe), you may use the @View annotation to filter what you want in the resulting object. I understand that you want something dynamic so it’s a bit more complicated. You will find what you are looking for here: http://www.cowtowncoder.com/blog/archives/2011/02/entry_443.html … Read more
After digging a bit I quickly found out there are basically two options: Option 1 You pass a “wrapper object” containing all the other parameters to the service. You might need to annotate this wrapper class with JAXB annotations like @XmlRootElement in order for this to work with the Jettison based provider, but if you … Read more
It isn’t quite out of the box but CXF does support JSON bindings to rest services. See cxf jax-rs json docs here. You’ll still need to do some minimal configuration to have the provider available and you need to be familiar with jettison if you want to have more control over how the JSON is … Read more
Your ProfileDto class is not referenced in SearchResultDto. Try adding @XmlSeeAlso(ProfileDto.class) to SearchResultDto.
You have to create a binding file as below, this will get applied globally and use it as wsdl2java – b “bindings.txt” “wsdl” <jaxb:bindings version=”2.1″ xmlns:jaxb=”http://java.sun.com/xml/ns/jaxb” xmlns:xjc=”http://java.sun.com/xml/ns/jaxb/xjc” xmlns:xs=”http://www.w3.org/2001/XMLSchema”> <jaxb:globalBindings generateElementProperty=”false”/> </jaxb:bindings>
You need to create a file named org.apache.cxf.Logger (that is: org.apache.cxf file with Logger extension) under /META-INF/cxf/ with the following contents: org.apache.cxf.common.logging.Log4jLogger Reference: Using Log4j Instead of java.util.logging. Also if you replace standard: <cxf:bus> <cxf:features> <cxf:logging/> </cxf:features> </cxf:bus> with much more verbose: <bean id=”abstractLoggingInterceptor” abstract=”true”> <property name=”prettyLogging” value=”true”/> </bean> <bean id=”loggingInInterceptor” class=”org.apache.cxf.interceptor.LoggingInInterceptor” parent=”abstractLoggingInterceptor”/> <bean id=”loggingOutInterceptor” … Read more
Include cxf-rt-transports-http-jetty jar in the maven pom.xml will solve the problem. <dependency> <groupId>org.apache.cxf</groupId> <artifactId>cxf-rt-transports-http-jetty</artifactId> <version>2.7.6</version> </dependency>
The problem is that JAX-RS dictates that parameter unbundling be done in one of two ways: The parameter bean has a public constructor that accepts a String The parameter bean has a static valueOf(String) method. In your case, the Date is being unbundled via its Date(String) constructor, which cannot handle the input format your client … Read more
there is a working example of doing nearly the same thing here… http://camel.apache.org/cxf-proxy-example.html start with this, then drop your changes in one-by-one and see where it breaks…