From one of my recent posts in response to a question by Shaivya Easwaren on this subject (on the user list): I propose the following roadmap: 1) Fix task.tag a) Add "id" attribute b) Add "namespace" attribute to render the xmlns (so the wrapper <vxml> element that you have in the above example is no longer needed) 2) Make RDCs X+V aware a) Add a "xv" (or some such name) attribute that conditionally alters the component's FSM to behave as a voice form for a event handler from the X side. b) Not emit the <filled> content (this will bypass validation, confirmation and echo) in fsm-input.tag 3) Explore strategies to allow RDC validation, confirmation and echo in conjunction with X+V apps (this is somewhat above and beyond what the V currently does in X+V, but will be fun exploring) We will shoot for (1) and (2) in RDC 1.1.
Shaivya Easwaren has tried out the concept and has posted a proof of concept tutorial on the wiki (long URL, will get fragmented): http://wiki.apache.org/jakarta- taglibs/ReusableDialogComponents/Tutorials/IntegrateWithXHTML