Re: Fwd: CXF has graduated!
Kudos to Dan and all people who has been involved. On Wed, Apr 16, 2008 at 1:26 PM, Arul Dhesiaseelan [EMAIL PROTECTED] wrote: Congratulations Dan and team! Daniel Kulp wrote: Forwarding this to cxf-user as it's as important for them as well. Dan -- Forwarded Message -- Subject: CXF has graduated! Date: Wednesday 16 April 2008 From: Jim Jagielski [EMAIL PROTECTED] To: [EMAIL PROTECTED] I am happy and proud to announce that at this month's board meeting, we have approved CXF's graduation out of the Incubator and as a TLP. Dan Kulp was approved as VP of the PMC. Congrats to one and all! --- -- David Castañeda R.
Re: NTLM Support?
check this, maybe it can helps, http://www.nabble.com/-CONF--Apache-CXF-2.0-Documentation:-Client-HTTP-Transport-(including-SSL-support)-(page-edited)-td16377827.html On Wed, Apr 2, 2008 at 9:23 AM, mrusso [EMAIL PROTECTED] wrote: I can't seem to find anything related to configuring CXF to support NTLM. Has anyone tried this or found any documentation / examples that they could point me towards? I'm trying to consume a Custom Microsoft SharePoint Web Service from our Java Portal (Spring / Hibernate on WebSphere) over SSL with NTLM. I'm told by the SharePoint admins that I can use Basic Authentication, but my tests have shown that it keeps asking me for NTLM credentials. I'm generating a client from a provided .WSDL. My plan is to work from the ground up, starting with No SSL, No Authentication. Add Authentication to the SharePoint instance, retest, add SSL, retest, etc. Rinse, Repeat. My initial tests tell me that OOB CXF doesn't talk nicely with Integrated Windows Authentication, but I'm pretty new to this arena, so I'm not ruling out user error. I've followed this process with Axis2 with some success, but the generated files are horrendous, and we already are using CXF to serve to a flex client, so I'd like to keep it in the family, so to speak. Thanks for your time, Mario -- View this message in context: http://www.nabble.com/NTLM-Support--tp16447079p16447079.html Sent from the cxf-user mailing list archive at Nabble.com. -- David Castañeda R.
Re: Handling internal errors via SOAP faults
Glen, I have been fighting against this sort of questions from several weeks now, I start a sample project that is on Jira about correct handling, unfortunately I haven't found an answer from someone who know, neither I have found the way to produce correct code for server, client faults. Anyway my idea, is to only expose the exception that can be handled by the client, like InvalidCountryNameFault or MaxRequestQuantityOverLimit, mark these as Client Fault, and any other exception like (RuntimeException), DBNotAvailable, etc (things client can't handle, ServiceException) as a general exception marked as Server Fault, but as I said, I haven't found the way to do this. Regards, -- David Castañeda R.
Re: CXF Spring Transactions
Can you explain it? how is your configuration now? On Wed, Mar 5, 2008 at 8:36 AM, Michael McCaskill [EMAIL PROTECTED] wrote: I have found the root of the problem, which fortunately isn't CXF related but a Spring-AOP (AspectJ) problem. Thanks. -- View this message in context: http://www.nabble.com/CXF---Spring-Transactions-tp15814197p15850223.html Sent from the cxf-user mailing list archive at Nabble.com. -- David Castañeda R.
Re: soap fault question
Hi, I'm still fighting with fault generation... can anybody give me a pointer where to get some examples or some information about this? in a service that I'm exposing, I'm trying to do SoapFault fault = new SoapFault(message, SoapFault.FAULT_CODE_CLIENT); throw fault; but it always end in ... soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; soap:Body soap:Fault faultcodesoap:Server/faultcode faultstringMessage is OK/faultstring /soap:Fault /soap:Body /soap:Envelope I'm expecting to produce a Client Fault but soap:Server is returned. I'm using a jaxws:endpoint -- David Castañeda R.
Re: soap fault question
Ready to go!... https://issues.apache.org/jira/browse/CXF-1434 hope this help, any further help I can provide don't hesitate in asking. -- David Castañeda R.
Problem with xsi:type=xsd:dateTime in request to a JAXWS using Date parameter.
Hi, can anybody point me out how to solve this issue... https://issues.apache.org/jira/browse/CXF-369 as maomaode writes the solution is to use annotation appinfo jxb:property jxb:baseType jxb:javaType name=java.util.Date /jxb:javaType /jxb:baseType /jxb:property /appinfo /annotation but I don't understand where to put this in CXF configuration xml I'm using something like this. jaxws:endpoint address=/op/xService implementorClass=com.xServiceImpl jaxws:implementor ref bean=wsXService/ /jaxws:implementor /jaxws:endpoint and in a call to an operation defined in this service the problem arise... xsd:dateTime becomes XMLGregorianCalendarImpl when Date needed If anybody can point me to some documentation I will be more than enough, I hope I already check this: http://cwiki.apache.org/CXF20DOC/jax-ws-configuration.html ... but still don't get it. -- David Castañeda R.
Re: soap fault question
In a previous thread some ask for other samples projects ideas... what are the possibilities of adding a sample of fault handling (Soap Fault Handling, @WebFault). I have been trying for long to implement correct fault handling, but :(, or maybe some more explicit documentation.. so I can create that sample project. If any body want me to do it... I could create a first template so any body with the knowledge would provide the exception handling missing parts. regards, -- David Castañeda R.
