wsdl2java + choice (one or both )

Hello: I'm using Apache CXF 2.7.3 I've having problems to generate JAXB classes from XSD that cointains this element xs:choice xs:sequence xs:element name=X type=xs:string/ xs:element name=Y type=xs:string minOccurs=0/ /xs:sequence xs:element name=Y type=xs:string/

Re: Best practice of using external WS-Policy files with CXF?

Hi Andrei, This does mean the policy imported in option c could be using: - option a: wsdl already contains wsp:PolicyReference URI=#policyId/ so the policy applied at runtime will define actual wsp:Policy wsu:Id=policyId or - option b: policyattachemnt element and CXF should still work

JAX-RS 2.0 compliance

Hi again. As part of my POC (that ultimately is aimed at aiding us to choose between CXF, CXF+Camel or Jersey) I'm now trying to port some use cases from Jersey to CXF. It was going very well except for a use case where I'm using javax.ws.rs.client.ClientBuilder, but it seems that this class is

Re: JAX-RS 2.0 compliance

Hi, CXF 3.0.0-milestone1 has just been released, give it a try please Thanks, Sergey On 26/11/13 10:49, António Mota wrote: Hi again. As part of my POC (that ultimately is aimed at aiding us to choose between CXF, CXF+Camel or Jersey) I'm now trying to port some use cases from Jersey to CXF.

Re: JAX-RS 2.0 compliance

Note, new Client API is in cxf-rt-rs-client module Sergey On 26/11/13 10:58, Sergey Beryozkin wrote: Hi, CXF 3.0.0-milestone1 has just been released, give it a try please Thanks, Sergey On 26/11/13 10:49, António Mota wrote: Hi again. As part of my POC (that ultimately is aimed at aiding

Re: JAX-RS 2.0 compliance

On 26/11/2013 11:58, Sergey Beryozkin wrote: Hi, CXF 3.0.0-milestone1 has just been released, give it a try please Hey, great news: I haven't heard anything yet about this (not even from announce@) and http://cxf.apache.org/download.html does not show anything new... Anyway, is there any

Re: JAX-RS 2.0 compliance

Yes, I just found out http://cxf.apache.org/docs/30-migration-guide.html But the problem is, how stable is this and what's teh roadmap until Release? If I tell my boss to use a Milestone1 he'll laugh... Nevertheless I will do test, I'll be happy if I can help somehow. Cheers. * Melhores

Re: JAX-RS 2.0 compliance

Hi On 26/11/13 11:02, Francesco Chicchiriccò wrote: On 26/11/2013 11:58, Sergey Beryozkin wrote: Hi, CXF 3.0.0-milestone1 has just been released, give it a try please Hey, great news: I haven't heard anything yet about this (not even from announce@) and http://cxf.apache.org/download.html

Re: JAX-RS 2.0 compliance

On 26/11/2013 12:19, Sergey Beryozkin wrote: Hi On 26/11/13 11:02, Francesco Chicchiriccò wrote: On 26/11/2013 11:58, Sergey Beryozkin wrote: Hi, CXF 3.0.0-milestone1 has just been released, give it a try please Hey, great news: I haven't heard anything yet about this (not even from

Re: JAX-RS 2.0 compliance

Hi On 26/11/13 11:16, António Mota wrote: Well, the services works well, however I detected some points: That was fast :-) - if I point to my root address as before it still give me the address of the WADLs and WSDLs. The WSDL links still work but the WADLs give a 404 Yes, WADL

Re: JAX-RS 2.0 compliance

Opps, I just answered it on my own question, please see my other post. Thanks for your excelent support :) * Melhores cumprimentos / Beir beannacht / Best regards * *__* *António Manuel dos Santos Mota http://gplus.to/amsmota*

Re: JAX-RS 2.0 compliance

Hi On 26/11/13 11:32, António Mota wrote: Sorry, @PreMatching does work, after I registered it in my javax.ws.rs.core.Application instead of rootContext. That leads me to a question however. Why do I have to register my classes with the JAXRSServerFactoryBean itself and not doing it only has

Question about CXF Fediz 1.1.0 and certificates

Hi all, Congrats for the job, this is a very nice feature, very useful ! I have some questions about certificates. There are a lot of certificates used in Fediz, and I do not understand how it works. This is problematic because I would like to generate and use my own REALM-name. Could you please

Re: Obtaining HttpSession from JAX-WS OutInterceptor

Thanks Dan. This worked perfectly for me. -- View this message in context: http://cxf.547215.n5.nabble.com/Obtaining-HttpSession-from-JAX-WS-OutInterceptor-tp563485p5736986.html Sent from the cxf-user mailing list archive at Nabble.com.

RE: Question about CXF Fediz 1.1.0 and certificates

Hi Joel Let us know whether the following page addresses your certificate related questions: http://svn.apache.org/viewvc/cxf/fediz/tags/fediz-1.1.0/examples/samplekeys/HowToGenerateKeysREADME.html?revision=1538770view=co Comment out the property trustedIDPs of the bean idp-realmA in

Re: Optional boolean matrix parameter with REST service possible?

Np. Please vote for https://java.net/jira/browse/JAX_RS_SPEC-437 Thanks, Sergey On 25/11/13 17:04, Christian Balzer wrote: Thanks for the clarification and help! Christian On Mon, Nov 25, 2013 at 4:11 PM, Sergey Beryozkin sberyoz...@gmail.com wrote: I've asked for some clarifications on it,

Re: JAX-RS 2.0 compliance

Hi again. Sorry for not having explained myself correctly. What I'm trying to do is to have CXF+Spring configured in a Servlet 3 non-xml fashion. SO I have my WebApplicationInitializer initializing a AnnotationConfigWebApplicationContext with some @Configuration classes. SO I have not only to

Re: JAX-RS 2.0 compliance

Hi On 26/11/13 13:41, António Mota wrote: Hi again. Sorry for not having explained myself correctly. What I'm trying to do is to have CXF+Spring configured in a Servlet 3 non-xml fashion. SO I have my WebApplicationInitializer initializing a AnnotationConfigWebApplicationContext with some

Re: JAX-RS 2.0 compliance

That was complicated... I tested like this: 1) removed factory.setServiceBean(testService()); it throws a org.apache.cxf.service.factory.ServiceConstructionException: No resource classes found 2) in my Application changed s.add(TestService.class) - a interface - to s.add(TestService

Re: JAX-RS 2.0 compliance

Hi On 26/11/13 17:06, António Mota wrote: That was complicated... I tested like this: 1) removed factory.setServiceBean(testService()); it throws a org.apache.cxf.service.factory.ServiceConstructionException: No resource classes found 2) in my Application changed s.add(TestService.class) - a

Re: SAML2 RACS for signed responses

Hi Thanks for reporting the issue, appears to be a bug in CXF or at the lower level. I guess the KeyInfo is typically available on the WS path hence the issue arises when it is not included. I can suggest a workaround for now, till the problem has been resolved:

Re: Ordering of wsdl method parameters changed for java-first services

Does anyone know which ordering of wsdl method parameters is correct? unicyco wrote I run a JAX-WS java-first web service. When I stepped up from an old Servicemix release to Karaf 2.3.1 with CXF 2.7.6, I noticed that the ordering of the parameters in the generated wsdl changed from the

Re: Ordering of wsdl method parameters changed for java-first services

I believe it should be in the order of the parameters on the method. As far as I’m aware, we haven’t done anything to change this as this is part of the JAX-WS spec. I’m not sure why it would have not been that way for you. Dan On Nov 26, 2013, at 5:45 PM, unicyco husby...@umn.edu wrote:

Re: Ordering of wsdl method parameters changed for java-first services

Thanks Dan. I appreciate the response. I'm positive something changed between CXF 2.7.6 and 2.7.7 that affected the generated wsdl from using an alphabetical ordering back to the method ordering. I've tested by launching karaf and viewing the generated wsdl, and the param order differs based on