Hi Dali, SCA doesn't generate fault elements in the wsdl at the moment. The steps to do so would be something like:
1. decide what you want the definition to look like within the service. I expect you would choose to define an @exception annotation and then put on that annotation whatever other information you'd want that you need for generating the fault elements within the wsdl. 2. Alter the wsdl generation so that it responded to these exceptions and generated the fault elements. 3. Alter both the service and the client end of the soap binding so that if the service threw one of the named exceptions, SCA would turn that into a soap fault; then on the client end that soap fault would be turned back into an exception. The aim would be that the client never needs to know if the service is local - i.e. running in the same PHP engine, on the same call stack - or remote. 4. Do all that in a way that in principle would also work for any of the other bindings i.e. nothing soap-specific appearing in the interface to the service or the client. That would be an interesting project. You would be very welcome to have a try and I could give you more pointers to where things happen in the code. If you wanted to, and if you were willing and able to sign up to the contributor's license, you could then contribute the code to the project. Matthew On Feb 5, 12:48 am, Dalibor Andzakovic <[EMAIL PROTECTED]> wrote: > Is there any way to generate wsdl:fault elements with SCA? If not > where would be a good place to start? > > TIA > > dali --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "phpsoa" group. To post to this group, send email to phpsoa@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.co.uk/group/phpsoa?hl=en -~----------~----~----~----~------~----~------~--~---
