Hi Josh,
The last downloadable release (v 1.1) supports Wicket 1.3, and current
trunk (1.2) supports Wicket 1.4. Some days ago Dan created a branch in which
I'll try to migrate to Wicket 1.5 in the near future.
From time to time, a new issue pops in the issue tracker, so I can say
some
Hi
Thanks for that Nick. I guess I will investigate more on this, actually i
did get to lookup Dynamic Forms and then linked to WWB.
I will do some homework on this topic and bounce any questions. Thanks for
that
Niv
On Tue, Aug 17, 2010 at 11:11 AM, Nick Heudecker nheudec...@gmail.comwrote:
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Re-Wicket-Web-Beans-tp2326481p2327733.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr
in context:
http://apache-wicket.1842946.n4.nabble.com/Re-Wicket-Web-Beans-tp2326481p2326481.html
Sent from the Wicket - User mailing list archive at Nabble.com.
/
And the source code for the examples here:
http://code.google.com/p/wicket-web-beans/source/browse/#svn/trunk/wicketwebbeans-examples/src/main/java/com/googlecode/wicketwebbeans/examples
Hth,
Daniel
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Re-Wicket-Web-Beans
this message in context:
http://apache-wicket.1842946.n4.nabble.com/Re-Wicket-Web-Beans-tp2326481p2327195.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
It sounds like what you're after is a dynamic form. This has been discussed
several times on the list and used to be detailed in the wiki. It's pretty
straightforward to implement. Hopefully this gives you an implementation
option.
On Mon, Aug 16, 2010 at 7:17 PM, Nivedan Nadaraj
the input if the datatype changes ?
Don't think WWB allows that easily.
Cheers,
Daniel
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Re-Wicket-Web-Beans-tp2326481p2327733.html
Sent from the Wicket - User mailing list archive at Nabble.com
Ahh interesting thanks for telling
2009/5/21 John Patterson jdp2...@gmail.com:
I just tried it out on 1.4 with no problems. It took about 2 minutes to edit
the source - mainly by changing getModel() to getDefaultModel() etc
Dan Syrstad-2 wrote:
I think Daniel was going to start work on
danisevsky danisevsky danisevsky at gmail.com writes:
Hi
I wanted to try Wicket Web Beans 1.1 upload example but I get the following
exception
.
Is Wicket Web Beans 1.1 incompatible with Wicket 1.4 rc4 or is reason of
exception something else?
Thanks for reply
Hi,
Are there a trunk or something.. I'd really like to try it out. But im
not going back to 1.3 todo it :)
2009/5/20 Daniel Toffetti dto...@yahoo.com.ar:
danisevsky danisevsky danisevsky at gmail.com writes:
Hi
I wanted to try Wicket Web Beans 1.1 upload example but I get the following
I think Daniel was going to start work on the Wicket 1.4 migration on the
trunk sometime in the near future. Currently the trunk supports 1.3.5.
-Dan
On Wed, May 20, 2009 at 3:20 PM, nino martinez wael
nino.martinez.w...@gmail.com wrote:
Are there a trunk or something.. I'd really like to try
I just tried it out on 1.4 with no problems. It took about 2 minutes to edit
the source - mainly by changing getModel() to getDefaultModel() etc
Dan Syrstad-2 wrote:
I think Daniel was going to start work on the Wicket 1.4 migration on the
trunk sometime in the near future. Currently the
I have fixed the Localizer problem and committed it to the trunk. Thanks for
pointing out the problem!
-Dan
On Tue, May 27, 2008 at 1:19 AM, Johan Compagner [EMAIL PROTECTED]
wrote:
getLocaliazer() in a constructor cant be done i guess because it will
nog be able to find any resources, expect
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
Hey Dan, thanks for the help. I found out what's going on, I was
declaring all the actions in the actions bean property, and that somehow
affected the ordering. After I removed all but the actions which should
not appear (those with a minus before the action name), it worked fine!
Thanks again!
Congrats, and wonderful work!
I really hope this project takes off and is adopted by the wicket community!
On Jan 14, 2008 6:57 AM, Dan Syrstad [EMAIL PROTECTED] wrote:
Wicket Web Beans 1.0 (final) has been released. Wicket Web Beans (WWB) is an
Apache Wicket component toolkit for displaying
+1, ditto
I'm using WWB as a demo on how life as a webdeveloper should/could be.
The only thing that would keep me from implementing it in projects now
is the lack of good documentation (even the tutorial on the website is
still partially in progress) and the small community that is using it.
But
Congrats!
Eelco
On Jan 14, 2008 4:57 AM, Dan Syrstad [EMAIL PROTECTED] wrote:
Wicket Web Beans 1.0 (final) has been released. Wicket Web Beans (WWB) is an
Apache Wicket component toolkit for displaying and editing POJOs that
conform to the JavaBeans specification. Web pages are automatically
Hi Daniel,
If you check out the latest from the SVN branch branches/wicket-1.3-port, it
builds with maven/1.3.0-beta4. The trunk is still for Wicket 1.2.6. The
head of both the trunk and 1.3 branch are techinically
wicketwebbeans-1.0-rc2SNAPSHOT.
-Dan
On 10/12/07, dtoffe [EMAIL PROTECTED]
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
36 matches
Mail list logo
