Last days I’ve been struggling with the dmfx:docbaseobject in the wdk 5.3.
Because I wanted more control on the layout of the attributes, I choose to create the attributes one by one in the jsp, instead of using the attributelist.
Snippet:
<dmfx:docbaseobject name='current_document' />
<tr><td>
<dmfx:docbaseattribute name='attr_obj_id' object='current_document' attribute='r_object_id' col1="</td><td>" />
</td></tr>
<tr><td>
<dmfx:docbaseattribute name='attr_medewerkercode' object='current_document' attribute='medewerkercode' size='12' col1="</td><td>" />
</td></tr>
This piece of code resides in a component-page. I have created a button that refreshes the page and changes the docbaseobject’s id. When re-rendering, the old values of the attributes remain on the page. This has to do with the internal workings of the DocbaseAttributeValueTag.
The problem lies in the renderEnd code, which does something like this:
DocbaseAttributeValue value = (DocbaseAttributeValue) getControl();
if(obj.isADocbaseObjectInstance())
{
strValue = value.getValue();
if(strValue == null)
{
IObjectAdapter objectAdapter = obj.getObjectAdapter();
if(objectAdapter != null)
{
strValue = getValueFromObjectAdapter(objectAdapter);
} else
{
strValue = getValueFromDocbaseObject();
}
value.setValue(strValue);
bGotDisplayValuesForRepeatingAttr = true;
}
}
It acutally reads the value directly from it’s control class. But once the value inside the control class gets set to somethinh other than null, the object is no longer updated.
This is how I worked around it.
I created a extra boolean value “m_reloadFromDocbase” in the control class and in the DocbaseAttribute class, and added these lines in the renderEnd
if (value.getReloadFromDocbase())
strValue = null;
This ensures the value of the attribute will get reloaded from the docbase.
In the behaviour class that handles thes jsp, the render-code is a little extended:
DocbaseAttribute dat = (DocbaseAttribute) getControl( "attr_" + attribute, DocbaseAttribute.class );
dat.setReloadFromDocbase( true );
The attribute comes form analyzing the page, using a FindValidAttribute visitor. If the boolean is set to false, the filled-in value will remain.
If you are interested in more detail, please dorp me a line [still figuring out howto]
) and comments are welcome too.
