Handling internal errors via SOAP faults

Hello, I have a general question for WSDL design regarding internal web service errors not the fault of the SOAP client request, such as database unavailable or system down or whatever. For example, let's say I have a simple GetCapital web service that takes a country and returns the name of its

RE: CXF Osgi bundle problem

It's working now with Equinox, thank you :) -- View this message in context: http://www.nabble.com/CXF---Osgi-bundle-problem-tp15880268p15891150.html Sent from the cxf-user mailing list archive at Nabble.com.

Re: Accessing WebService that requires username/password

xbranko wrote: For me the problem is that I do not have access to the server, i.e. I have to do everything from the client side. Also javax.xml.ws.Service class does not have a default constructor, but rather only protected constructor that takes java.net.URL wsdlDocumentLocation and QName

Re: Nordic charaters problem in SOAP/MQ

WIndows does not have a code page for UTF-8. If you want to display UTF-8, you have either send UTF-16 to the 'W' API or convert to some local code page. On Fri, Mar 7, 2008 at 2:54 AM, mr.andersen [EMAIL PROTECTED] wrote: Problem found and solved! First of all - thanks for the quick

AW: trying to use ClientProxyFactoryBean but failing

I can´t tell you whats going on, just wanted to mention that it seems that your problem is related to mine, which I originally postet under thread http://www.nabble.com/-2.0.4--Service-unit-tests-fail-after-upgrade-from-2.0.2-to15610639.html Somehow my last response on that thread didn´t make

Re: trying to use ClientProxyFactoryBean but failing

Your error is a bit strange. It looks like it could be one of: 1) The name/password might be wrong or something and the server is re-asking you to authenticate 2) The server might be sending a redirect. You might want to put a wireshark/tcpdump trace on it to see what the server is

Re: NullPointerException thrown by CXFServlet

Spring 2.5.2 or 2.0.x? This LOOKS like 2.5.2. Logged as bug: https://issues.apache.org/jira/browse/CXF-1435 Can you try the 2.0.5 snapshots and see if it's fixed? Yea, you would thing Spring 2.5.2 would be backwords compatible, with 2.5.1, but Dan On Thursday 06 March 2008,

Re: Accessing WebService that requires username/password

Unfortunately, this is a known issue. :-( Basically, for the SOAP communication, the http:conduit bean things in the config are used to pick up authentication things, ssl certs, etc... so a proper secure connection can be made to protect the data. Unfortunately, the WSDL retrieval part

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

Re: Handling internal errors via SOAP faults

In general, the jaxws way of doing this is to map the runtime exceptions to a very generic soap fault that is fault code SERVER and just the message (ex.getMessage()) is set into the fault message. On the client side, this ends up throwing the generic SOAPFaultException (but with the correct

interface and implemantation files under different package

Hi, If I put interface and implementation classes in different package, CXF doesn't expose all my methods in wsdl file. did any body has same problem before? do I need to add extra annotations in interface or implementation files? Thanks, Mehmet Connect with friends from any web

Re: Handling internal errors via SOAP faults

I use a fault called OperationFailedFault, and set its payload to the root exception's message: try { context.commitChanges(); } catch(Exception e) { context.rollbackChanges(); throw new OperationFailedFault(e.getMessage(), Commit failed, e);

Re: Accessing WebService that requires username/password

ianroberts wrote: If it's internally using the standard URL mechanism then have you tried registering a java.net.Authenticator to supply the username and password? http://www.javaworld.com/javaworld/javatips/jw-javatip46.html Ian That did it! This is good in simple case of

Re: Handling internal errors via SOAP faults

On Friday 07 March 2008, David Castañeda wrote: 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

Re: interface and implemantation files under different package

That would be very strange. I just attempted a quick test here and it worked fine. Is there any way you can send a testcase? Dan On Friday 07 March 2008, Mehmet Imga wrote: Hi, If I put interface and implementation classes in different package, CXF doesn't expose all my methods in wsdl

Re: AW: trying to use ClientProxyFactoryBean but failing

Your case is very different. I honestly have no idea how that would have worked even with 2.0.2. In your case, your client is specifically using the URL: http://localhost:8080/cxf/TestService However, your service is using some Mock thing that isn't opening up any port. The simple fix is

Re: NullPointerException thrown by CXFServlet

Yes, I am using spring 2.5.2 and with the latest 2.0.5 snapshot, the error went away and the service is now up and running. Thanks for your help. g dkulp wrote: Spring 2.5.2 or 2.0.x? This LOOKS like 2.5.2. Logged as bug: https://issues.apache.org/jira/browse/CXF-1435 Can you

RE: trying to use ClientProxyFactoryBean but failing

username/password are not wrong because I used the same username/password for each method and the first one works. I tried the change you suggested and now I get a different error. Does this give you any more info? ClientProxyFactoryBean factory = new ClientProxyFactoryBean();