Mime type parameter matching - or lack

Hi, We've noticed that CXF doesn't use mime type parameters for matching except for q and d. Is there a reason for this? Our goal is to use a parameter to influence the shape of json or xml that is returned. We had to create a @Feature to override the default sort model for method selection,

wsdl2java generates incorrect @XmlElement(namespace=“…”)

I am using Apache CXF 3.1.7, and the wsdl2java command is generating code with missing/incorrect namespace attributes on the @XMLEment annotation. Note I generally use four distinct namespaces within each WSDL document, which are as follows: • Shared data types across many WSDL

RE: Configuring 2way SSL on a REST endpoint in an OSGi container

Hi, If you would like to force client authentication, the property org.ops4j.pax.web.ssl.clientauthneeded is more appropriate, I guess. That means, the OSGi container will accept only client calls containing certificate trusted on container side. The property will activate client

RE: SAP Webservice: None of the policy alternatives can be satisfied

Hi, In case if SAP web service doesn't force special headers / security, you can just use generated service interface and set address in the factory explicitly, without using WSDL: JaxWsProxyFactoryBean factory = new JaxWsProxyFactoryBean();

Re: WadlGenerator - Bean validation support for complex types?

Sergey, Thanks for the hint - now I added the schema type reference detection for minLength/maxLength/pattern as example in SourceGenerator.java. I had to add a separate method to get all prefixes used in the WADL (createWadlPrefixMap(app)), as schemaCollections doesn't hold them