This capability is built into the SOAP processing model -- no need to use a separate controller framework. You should use a handler chain to check authentication/authorization.
Anne -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, May 21, 2004 6:43 AM To: [EMAIL PROTECTED] Subject: web services controller Is there any "Controller" for web services? Do I need to have a different class for each web service and then do the security, authorization refactoring by myself? What I have: WS1 -> 1 class W1 -> calls methods in a predefined and obliged order WS2 -> 1 class W2 -> calls methods in a predefined and obliged order What I had in mind (just like Struts): WS1 ... WSn -> Controller -> check authentication/authorization -> dispatch to a class that consumes the web service and sends a response. Struts would be the right answer because but I am not processing HTTP requests... so :( If nothing has been implemented, does anyone know of any good material regarding this? (the google search gave me some solutions/proposals but with complex architectures) Thank you in advance, Pedro Salgado
