Webservice configuration

[clebrun]

Hi,

I am building my first PureMVC app, and I am more familiar with Mate.

My app is reading a XML config file at startup. This XML config file contains the location of a webservice WSDL. Then, my app has to query some web methods  of this webservice.

Here are my question: I am implementing a Proxy per WebMethod, but in each of these Proxy I am initializing a WebService (Load WSDL ...) using the config oject I pass in the notification.
Is there a way to avoid this ? By initializing only one WebService and using it in the differents Proxy ?

Thanks !

[puremvc]

First, is it really necessary to have separate proxies for each method? Usually the Proxies are one per data type. So if you had several methods for CRUD functionality for an object type, you'd handle them all in one Proxy.

Now if you have lots of disparate data types being managed by the same service, then yes, you'd need multiple Proxies talking to the same service.

In that case you probably want to create a Delegate class that has the service and method definitions and have each Proxy instantiate a Delegate and use it for making the calls.
You can see an example of a Delegate in the Cafe Townsend Flex Demo.

-=Cliff>

[clebrun]

Thanks for your answer.

I need separates proxies because even if all web methods return XML, their meaning is different :

The first method called is to authenticate the user. So I after receiving the result, I only need to send an event to know if authenticate succeed or not.
The other methods called return XML data that I parse to create different VO, depending of the called method.


About my "problem" of webservice instantiation, here is how I did :
- First, using a ConfigProxy, I read from a config file the webservice URL
- In this ConfigProxy, when I receive the result, I instantiate a WebserviceProxy with the received URL
- Then, in the other proxies, I retrieve this WebServiceProxy and use it to call the different web methods

But I am not sure it is the best practice ...

[puremvc]

This will work. It is essentially implementing a Delegate in a Proxy. But if there are multiple calls that may go out at once you need to manage it closely to ensure the responses go back to the original caller. This is where the Delegate pattern is a little better, since each Proxy has its own Delegate instance with its own service instance.

-=Cliff>