On 9/15/07, Zenrique Steckelberg [EMAIL PROTECTED] wrote:
- allow constructor to accept models besides beans too, if possible.
Me too! :-)
Or is there some other way to use DetachableModels backed by JPA with WWB?
(The abbreviation conjures images of a tiny but venerable local
railroad company
On 9/17/07, Gabor Szokoli [EMAIL PROTECTED] wrote:
On 9/15/07, Zenrique Steckelberg [EMAIL PROTECTED] wrote:
- allow constructor to accept models besides beans too, if possible.
Me too! :-)
Or is there some other way to use DetachableModels backed by JPA with WWB?
(The abbreviation
Dan Syrstad wrote:
Sounds like this may be a caching issue - I'm not sure. Can you send me
your
beanprops file directly?
-Dan
Its the following, where marca field gets it options from database, and
temperaturaArmazenagem gets them from an enum:
Produtos {
actions: incluir,
For me databinder helps cut the boilerplate code, just as WWB. I just add
annotations to my domain model, and databinder does the rest. It's WWB for
the database side of the app! Imagine putting both working together. I was
able to create CRUD pages with the least amount of code ever. Less
Although it may blur the lines between view and model, there are a number of
reasons that it still could be the right direction.
* centralized configuration. all view configuration is in the same file as
your model code.
* leverage Java syntax instead of custom DSL. easy for users to get up and
I do control my crud list and detail pages with annotations on the
model, and it works quite nice (although I can't say the panels
constructing the data table and form belongs in the category pretty
code, at least there isn't a lot of it). I find I often use multiple
views of the same model
I'm really impressed with your work, and just want to impart what's worked
*really* well for me. Good luck with whatever direction you take.
One thing Dan could consider is to abstract enough so that both
strategies could be supported. Doesn't mean he should ship annotations
support, but it
Ryan:
One thing I started considering today after your comments was to place
annotations, similar to beanprops, on the component level (e.g., Page).
Currently beanprops are associated with the Page anyway, so this would be
natural and provide type-safeness without bluring the view/model line.
I
My suggestions to this nice compont:
- allow beanprops files to be reloaded while app is running. How it stands
now I have to restart the app everytime a change to beanprop file is made,
it can be time consuming.
- allow constructor to accept models besides beans too, if possible. I am
trying to
Hi Zenrique:
See below...
-Dan
On 9/15/07, Zenrique Steckelberg [EMAIL PROTECTED] wrote:
My suggestions to this nice compont:
- allow beanprops files to be reloaded while app is running. How it stands
now I have to restart the app everytime a change to beanprop file is made,
it can be time
In the current WWB strategy, required fields are enforced in your model/DAO
layer. For example, if you click your Save action, the action on your page
would be invoked. This, in turn, calls your DAO or model. Often fields are
conditionally required based on use case and or data conditions. We're
Hi Dan,
Does your framework support drill down feature in case I have a ListBean
as a property in my parent bean so that it can also generate a listview of
form fields based on that properties of the Child Bean collection ?
if there is also a way to customize the drill depth, it will also be
Hi Ayodeji:
See my responses below...
-Dan Syrstad
http://wicketwebbeans.sourceforge.com
On 9/13/07, Ayodeji Aladejebi [EMAIL PROTECTED] wrote:
Hi Dan,
Does your framework support drill down feature in case I have a
ListBean
as a property in my parent bean so that it can also generate a
Hey Dan, that looks very nice! Thanks for sharing.
Eelco
On 9/12/07, Dan Syrstad [EMAIL PROTECTED] wrote:
In response to Jonathan Locke's blog entry entitled Wicket on Wheels (
http://web.mac.com/jonathan.locke/iWeb/JonathanLocke/Blog/6B9496DF-4AF1-455E-B94C-652709275041.html),
I have
Hi Dan,
It looks very powerful! BTW, why chose to use a config file (beanprops)
instead of Java code?
I think doing in Java for everything other than the standard web stuff
(HTML/CSS/js) is a
basic principle of Wicket.
--
View this message in context:
Hi Kent:
Thank you for your kind comments! It's nice to see several months of work be
useful to others.
I've heard the why not Java instead of beanprops comment before. I may
even do something about it ;-). Seriously, that may be offered as an
alternative to the beanprops file.
I chose the
16 matches
Mail list logo
