Please take this CXF related discussion to CXF mailing list (or discuss outside axis2 list).
Deepal > Hi Martin, > > Did you create a Jira for this issue of camelcase namespaces in CXF? I > didn't see any reference to this elsewhere. What went wrong? > > Thanks, > > - Dennis > > > On 07/08/2012 01:10 AM, Martin Gainty wrote: >> Good Morning Dan >> >> we had a serious issue with CXF handling of camelcase namespaces >> which caused generation of CXF service and CXF client to fail..we >> refactored the service and client to Axis >> Do you know if the CXF committers fixed CXF wsdl2code handling of >> camelcase namespace so CXF based WSDLS wsdl2code generates working code? >> >> Martin Gainty >> ______________________________________________ >> Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité >> >> Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene >> Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede >> unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. >> Diese Nachricht dient lediglich dem Austausch von Informationen und >> entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten >> Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den >> Inhalt uebernehmen. >> Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le >> destinataire prévu, nous te demandons avec bonté que pour satisfaire >> informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie >> de ceci est interdite. Ce message sert à l'information seulement et n'aura >> pas n'importe quel effet légalement obligatoire. Étant donné que les email >> peuvent facilement être sujets à la manipulation, nous ne pouvons accepter >> aucune responsabilité pour le contenu fourni. >> >> >> >> ------------------------------------------------------------------------ >> Date: Fri, 6 Jul 2012 14:56:51 -0400 >> From: dee...@opensource.lk >> To: java-user@axis.apache.org >> Subject: Re: CXF / Metro / Axis2 >> >> Hi Danny, >> >> I guess you have already made the choice to pick either CXF or Metro >> (which is not a bad choice at all). All the three frameworks are good >> and all have pros and cons (much more than you have listed). However, >> without knowing your requirements I cannot recommend any of those. >> All three are good for Web services, but when it comes to specific >> features one become better over other. >> >> Any service you deploy is automatically exposed as both REST and SOAP >> (and also both WSDL 1 and 2). We do not use WSDL behind the seen, >> however we do provide much better way to customize REST binding using >> WSDL 2.0. >> >> I am not going to comment about CXF and Metro, because it is unfair >> to comment on those in an Axis2 biased list. >> >> Deepal >> >> I was looking for a bit of information from experienced >> users of different java web services frameworks. >> Specifically, CXF, Metro, axis2 >> >> I have an new environment with many different web services: WSDL >> and REST, Java and .NET WCF >> So I've been trying to go through the specfics of each framework >> to determine which is the best >> for my environment. >> >> Here is what I've found, based on a few hours of googling. >> >> CXF - PROS - WSDL and REST (implements both JAX-WS and JAX-RS) >> - CONS - Doesn't support WSIT for the WSDL side of >> things, for WCF/Java interoperability >> >> Axis2 - CONS - REST support for only GET and POST (seems to use >> wsdl behind the scenes even for REST?) >> >> Metro - PROS- WSIT support on the wsdl side. >> - REST support if I include Jersey >> >> So it seems like CXF or Metro is a good choice, depending on how >> many wsdl services I think >> will be Java/WCF or WCF/Java. >> Any input, opinions, past experiences, corrections, etc, appreciated: >> >> Cheers >> >> >> -- >> Blog - http://blogs.deepal.org/ -- Blog - http://blogs.deepal.org/
