Greetings,

 I apologize if I'm bringing up an issue/question that's already been resolved/answered, but my searches on the Internet and the AJAX forums have turned up nothing.

 
My scenario is such -

 
I have a page I've constructed that is comprised of an Accordion control with 3 panes. In each of these panes exists 3-5 CascadingDropDown boxes. These boxes pull their data from a webservice, which in turn pulls its data from a dataset.

 
Up until today, I had been using the previous Atlas release with minimal problems. However, since some of the bugs that had bothered me in the Atlas release were addressed in the latest AJAX release, I made a move to upgrade. The transition went mostly fine, however, my CascadingDropDown boxes ceased to function when placed between the <Content> tags of the AccordionPane. This was not an issue in the previous Atlas release I was using.

 Thinking I had inadvertently broken my setup with some of the parameters, I started diagnosing the problem with a bare-bones form consisting of a simple Accordion with two panes, and a single CascadingDropDown box. The CascadingDropDown box populates when outside of the AccordionPane, however, as soon as it is placed in the <Content> section, it  does not populate. Additionally, I've set breakpoints at the start of the service method called, and these breakpoints are never reached, leading me to believe that the service is never called. The service responds with the correct return values when invoked manually through ASMX Service Description page.

 
I've read the migration guide and several blog and forum posts about transitioning from Atlas to the AJAX Beta release, none of which seemed to provide an answer for my question. Am I missing a new semantic that needs to be applied to the controls in certain contexts?

 
Again, my sincerest apologies if this has been addressed in the past and I'm resurrecting an old topic.