Hello,
I would like to ask a question which will help me customize
something in Chiba processor.
I have observed the following and would like feedback on
whether my observations are correct
in order to understand what is going on and proceed.
When the UI is generated what is passed in XSLTGenerator as
source (method generate) is
chibaBean.getXMLContainer(). (from
method buildUI of ServletAdapter)
However, this document is not updated with the latest changes
in GUI;
what I have observed as being updated instead is chibaBean.getContainer().
My question therefore, is how XSLTGenerator displays correct
data in GUI since chibaBean.getXMLContainer
does not seem to be up to date? Is there a connection
between XSLTGenerator and chibaBean.getContainer?
Example
--------------
I created a multipage-form similar to
wizard-with relevant sample. I
pressed ‘next-page’ trigger and before
generator.generate was called in method buildUI of ServletAdapter,
I printed the following values
DOMUtil.prettyPrintDOM(this.chibaBean.getContainer().getDefaultModel().getInstance("controller").getInstanceDocument());
DOMUtil.prettyPrintDOM(this.chibaBean.getXMLContainer())
In order to see the values in the controller instance
The first was
<wizard xmlns="" xmlns:chiba="http://chiba.sourceforge.net/2003/08/xforms"
xmlns:xforms="http://www.w3.org/2002/xforms" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<page1
relevant="no"/>
<page2 relevant="yes"/>
<page3
relevant="no"/>
</wizard>
while the other was
……
<xforms:instance id="controller" xmlns="">
<wizard>
<page1 relevant="yes" />
<page2
relevant="no" />
<page3
relevant="no" />
</wizard>
</xforms:instance>
…..
Can somebody explain to me how XSLTGenerator really works as
there is limited information in the Chiba cookbook?
Thank you
Giota
