AW: Strange problems with XFroms in OPS3.0

> Hello,
> I do have a more complex xforms instance. The idea behind that is to have a generic view to fill out a structured but undefined amount of parameter values.
> I pretend the use of several "pages" to the user by defining "pages" within the instance as page nodes. Those "pages" I select in my generic view via xforms:groups.
> I have to types of "pages". One type for "parameters" and an other for some "configuration" (that is just a node with some attributes at the moment). So I have defined two types of virtual pages by using groups in my view.
> To move between the "pages" I have got a previous and next button. A pipeline is at the moment only in use to debug the instance data (null-serializer).
>
> Here are my problems:
>
> 1)
> As long I remove or rename the "configuration" page nodes, it works with exception that I can overtake my readonly attributes used for the boundaries PageNo > 1 < PageMax by very quick pressing the buttons.
>
> 2)
> If I have the two "page" types in my instance it works fine also the first time I move from a "parameter page" type to a "configuration page" type. Going ahead to a next "parameter page" submits the instance to the null-serializer as expected but the view is not updated. A next try of pressing the next button causes the whole application to hang-up without any action or message neither in the console not in the browser.
> In each of  my "parameter pages" I have a test data aforms:input, a xforms:select and a xforms:selec1. When I remove the select and select1 in my view I can move through all pages but e.g. the "help" attributes are not working anymore.
>
> I tried to find a working solution in several ways e.g. using xforms:repeat or xforms:switch instead of groups with almost the same problems.
>
> Here is my view including the instance data.