This is one of the architectural best practices Cairngorm was designed to handle. Encapsulating service invocation through [Event >> Command >> Delegate >> Service] structure sounds like it will fit your needs. An easier, but more tightly coupled and limited solution, would be to declare your service in your mx:Application file, and then reference the service in any child components using Application.application.serviceID syntax. Some good resources: http://opensource.adobe.com/wiki/display/cairngorm/Cairngorm http://www.cairngormdocs.org/ (especially the 6 part article by Steven Webster) HTH, Ryan
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Eduardo Souza Sent: Tuesday, September 23, 2008 12:47 PM To: [email protected] Subject: [flexcoders] Using just one mx:WebService Hello Everyone, I'm working on a project wich uses a Web service on the server side (SOAP1.1). Now our team is studying to develop a client app. And we're developing an organizational software for our team by the way. But I got a problem. When I create my MXMLs files, I need to create a component (mx:WebService) on all of them. But I don't want that. I just want one mx:WebService component containing all of webservice operations and use just that to all of my MXMLs files. What I need to do? Thanks! (Sorry about my english. That isn't my primary language). This message is private and confidential. If you have received it in error, please notify the sender and remove it from your system.
