WebServices Queuing problem

[gumnam]

I have an RIA which has about 15 webservices to load. By the time user clicks
signin sometimes the wsdl is not loaded and hence its not making a call to
webservice method to authenticate user's credentials. SO My question is does
mx:Webservice ensure queuing up of calls untils the wsdl is fetched.


I come from flash world. And flash used to take care under the hood for
queuing up the webservice method calls untill the webservice wsdls were loaded.
Is that true for Flex WebServices instantiated through mx:Webservice tag ?

[Dave Wolf]

gumnam wrote:

> I have an RIA which has about 15 webservices to load. By the time user clicks
> signin sometimes the wsdl is not loaded and hence its not making a call to
> webservice method to authenticate user's credentials. SO My question is does
> mx:Webservice ensure queuing up of calls untils the wsdl is fetched.
>
>
> I come from flash world. And flash used to take care under the hood for
> queuing up the webservice method calls untill the webservice wsdls were loaded.
> Is that true for Flex WebServices instantiated through mx:Webservice tag ?
>
>
>

My bigger question is why are you rolling your own security rather then
implementing it via J2EE and letting Flex automatically and
transparently integrate into that.


You can control the order that controls are rendered in Flex using
either the creationComplete event or a creationPolicy.

<mx:ComboBox creationComplete="myService.send()"
dataProvider="{myService.result.types.type}"/>


But my first question is the core one.....

--
Dave Wolf
Cynergy Systems, Inc.
Macromedia Flex Alliance Partner
[url]http://www.cynergysystems.com[/url]

Email: [email]dave.wolf@cynergysystems.com[/email]
Office: 866-CYNERGY x85

[gumnam]

I am sorry but I did not understand your core concern.

Secondly, I understand that we can control things using creationComplete and
creationPolicy. In fact my code does that on click of the button and ofcourse
button is not going to be displayed until the creation is complete of the whole
application. But on my Application creationComplete it tries to load the wsdls
and since that operation is assyncrhronus in nature, by the time somebody
clicks on signin ,it might be the case that those wsdls are still being fetched
and the one thats needed for the servicemethod being called might not yet have
been fetched.

[Dave Wolf]

gumnam wrote:

> I am sorry but I did not understand your core concern.
>

My core concern is that you are rolling your own security. The fact
that you are validating a login via a web service call, rather then
letting the server manage your security. By doing it via a web service,
you now need to litter your UI code with security checks.

The J2EE container you use should manage your security. Just IMHO.

> Secondly, I understand that we can control things using creationComplete and
> creationPolicy. In fact my code does that on click of the button and ofcourse
> button is not going to be displayed until the creation is complete of the whole
> application. But on my Application creationComplete it tries to load the wsdls
> and since that operation is assyncrhronus in nature, by the time somebody
> clicks on signin ,it might be the case that those wsdls are still being fetched
> and the one thats needed for the servicemethod being called might not yet have
> been fetched.
>

I guess my point was, dont render the UI controls at all until the WSDL
is loaded. For instance, you could make a web service call and in the
result handler then cause your UI controls to render.


--
Dave Wolf
Cynergy Systems, Inc.
Macromedia Flex Alliance Partner
[url]http://www.cynergysystems.com[/url]

Email: [email]dave.wolf@cynergysystems.com[/email]
Office: 866-CYNERGY x85