I have solved it by creating a code generator, that for each POJO passed,
it makes physical html, java and properties files at given package path.
According to the template you pass to the generator, it can generate any
code for you.
Drawbacks
Once generated, there is no link between POJO and generated files, if
you change POJO,
you have to run the generator again, overwrtiting existing files at
given path.
Therefore it is necessary to move your files to another package
and once you add your custom code, transfer new generated changes by hand.
May not be the best approach, but this way you can fully customize
generated files,
they are the same files you woud prepare by hand, only automatically
generated.
Would you be interested in using such a tool? So far I have used it just
for me,
but can make it available at Github if you would like.
Regards
Vit Rozkovec
Dne 23.2.2015 v 17:10 ChambreNoire napsal(a):
Hey there,
In the case of large forms with 20+ fields, how should one go about coding
the wicket components? I have a large form of over 300 fields divided into
20 pages to code. Instantiating and wiring up each of these one by one would
take an age.
Any ideas?
Many thanks,
CN
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Large-forms-tp4669718.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
