PDA

View Full Version : scaffold doubles enum fields in create and update



mkolb
Nov 14th, 2009, 10:00 AM
Hello,
I'm using Roo 1.0.0RC3 and Spring 3.0.0RC2.
The views for enum fields are always generated two times.
Is there already a bug report for this or do I do anything wrong?


<div id="roo_firewallrule_protocol">
<label for="_protocol">Protocol:</label>
<form:select cssStyle="width:250px" id="_protocol" items="${fwprotocol_enum}" path="protocol"/>
<script type="text/javascript">Spring.addDecoration(new Spring.ElementDecoration({elementId : '_protocol', widgetType: 'dijit.form.FilteringSelect', widgetAttrs : {hasDownArrow : true}})); </script>
<br/>
<form:errors cssClass="errors" id="_protocol_error" path="protocol"/>
<form:select cssStyle="width:250px" id="_protocol" items="${fwprotocol_enum}" path="protocol"/>
<script type="text/javascript">Spring.addDecoration(new Spring.ElementDecoration({elementId : '_protocol', widgetType: 'dijit.form.FilteringSelect', widgetAttrs : {hasDownArrow : true}})); </script>
<br/>
<form:errors cssClass="errors" id="_protocol_error" path="protocol"/>
</div>
<br/>
<br/>
<div id="roo_firewallrule_port">
<label for="_port">Port:</label>
<form:select cssStyle="width:250px" id="_port" items="${fwport_enum}" path="port"/>
<script type="text/javascript">Spring.addDecoration(new Spring.ElementDecoration({elementId : '_port', widgetType: 'dijit.form.FilteringSelect', widgetAttrs : {hasDownArrow : true}})); </script>
<br/>
<form:errors cssClass="errors" id="_port_error" path="port"/>
<form:select cssStyle="width:250px" id="_port" items="${fwport_enum}" path="port"/>
<script type="text/javascript">Spring.addDecoration(new Spring.ElementDecoration({elementId : '_port', widgetType: 'dijit.form.FilteringSelect', widgetAttrs : {hasDownArrow : true}})); </script>
<br/>
<form:errors cssClass="errors" id="_port_error" path="port"/>
</div>

Stefan Schmidt
Nov 14th, 2009, 04:44 PM
No, you are not doing anything wrong. There is a bug in Roo RC3 which causes this issue: ROO-367 (https://jira.springsource.org/browse/ROO-367)

This has been addressed in Roo trunk and the fix will be available with the upcoming release of Roo RC4.

Cheers,
Stefan

mkolb
Nov 14th, 2009, 05:09 PM
Cool. I've build the current trunk and using it now. Problem is fixed.