微软服务器dda,Composite DDA

Composite DDA

08/23/2017

2 minutes to read

In this article

The composite data-driven adapter is an extension of the DDA architecture introduced with UII. It was built to address the issue where you can assign only one DDA type to an application. In some cases, an application might need different technologies provided by different data-driven adapters to access the required functionality. An example for this could be a Java applet in a web application. You can use the composite DDA in these scenarios.

Composite DDA bindings

The composite DDA bindings are similar to the other data-driven adapters. The bindings are simply added to a collection, which supports adding bindings of different types. The following sample shows a binding collection of three data-driven adapters. However, you can add only one collection per application.

DDAType1, DDAAssembly

…

DDAType2, DDAAssembly

…

DDAType3, DDAAssembly

…

Each of the tags can have an optional parameter prefix. This allows using the same control name in different binding sections. If prefix is defined, all controls in this DDA will have this prefix attached to their control name.

Note

Every DDA binding should always be called with its respective prefix. For example, if the DDAType2 and DDAType3 have a control defined with the name Button1, the control names used in the automation are dda1Button1 and dda2Button1.

Note

If the webpage contains a ActiveX control or Java Applet, the web application default action does not wait for the ActiveX control or Java Applet to load.

See also