Yes, the ordering changed a while back on the trunk (the change appeared in
1.0-rc2). It occurred due to a change in how actions are handled (hopefully
for the better). Anyway, you need to explicitly call out the actions and
properties in the beanprops "props" parameter (or @PropertyNames for
annotations). Actions are called out by saying: action.{action-name}.I believe the Sourceforge WWB mailing list is working. Other posts are coming through there. -Dan On Jan 23, 2008 9:45 AM, Zenrique Steckelberg <[EMAIL PROTECTED]> wrote: > > First of all, congrats for such a nice tool, WWB has saved me lots of time > in > one of my projects! > > I know it would be more appropriate to post this at WWB's mailing list, > but > I've sent an email 2 days ago but it seems it hasn't arrived there, so > I'll > try here: I've upgraded to the latest releases of Wicket (1.3.0) and > Wicket > Web Beans (WWB), everything went fine after I updated the bean prop files, > only thing is that the order of fields and action buttons in beantables > are > mixed now. They were respecting the order in which they were declared in > beanprop files before the upgrade. Has something changed in this versions > or > is it a bug? > > TIA, > > Zenrique Steckelberg >
