with an in-house web framework that made you code the HTML tags in
Java. No HTML, no JSP, just Java. It wasn't pretty ;-).
-Dan Syrstad
http://wicketwebbeans.sourceforge.com
On 9/12/07, Kent Tong [EMAIL PROTECTED] wrote:
Hi Dan,
It looks very powerful! BTW, why chose to use a config file
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
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
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
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
I've created a Wicket Web Beans mailing list on Sourceforge. For WWB-related
topics, you can subscribe to the mailing list at:
https://sourceforge.net/mail/?group_id=205206 . This will allow the Wicket
mailing list to focus on Wicket directly.
-Dan
In what area of the world and what are you looking to do?
-Dan
On 9/18/07, skatz [EMAIL PROTECTED] wrote:
Hi,
Can anyone provide me with pointers to individuals or companies providing
Wicket consulting/contracting or outsourced personnel?
TIA,
skatz
--
View this message in context:
On 9/20/07, dtoffe [EMAIL PROTECTED] wrote:
For most cases, the PropertyChangeEvents are ok. But now I'm facing a
particular problem and I guess I'm trying to use the wrong tool for the
task.
Let's say I have a bean with two properties and I want to show them as
dropdownchoices, but
On 9/21/07, Craig Lenzen [EMAIL PROTECTED] wrote:
Any interest in a Wicket User Group meeting in Minneapolis?
Count me in!
Register here, http://cwiki.apache.org/WICKET/community-meetups.html
http://cwiki.apache.org/WICKET/community-meetups.html
then detach the models for the current
component only.
-igor
On 10/1/07, Dan Syrstad [EMAIL PROTECTED] wrote:
Anyone know why Page.detachModels() no longer detaches the models of all
child components in 1.3beta3? There is a bunch of code commented out in
Page.detachModels
On 10/1/07, Kent Tong [EMAIL PROTECTED] wrote:
Dan Syrstad-2 wrote:
This has broken a JUnit test that was testing a detachable model using
WicketTester. The same test passes in Wicket 1.2.6. Is there something
different I should be doing in 1.3?
If it was calling detach() instead
(childModel.isAttached()); // Attached
}
}
On 10/2/07, Kent Tong [EMAIL PROTECTED] wrote:
Dan Syrstad-2 wrote:
Nope. I tried detach() too and that doesn't work - the test still fails.
I
had to write my own method which was basically was a copy of the old
Page.detachModels() code
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]
It seems to be working for me.
-Dan
On 10/15/07, Christopher Gardner [EMAIL PROTECTED] wrote:
Anyone having problems getting DatePicker to work in beta4? I get the
icon, but when I click nothing happens. Probably my error, but just
curious.
It appears that the issue http://issues.apache.org/jira/browse/WICKET-606
that was fixed in beta2 is broken again in beta4. Basically TextFields for
Strings (configured with the defaults) are always converting to empty
strings. They should convert to null by default based on the
.
johan
On 11/2/07, Dan Syrstad [EMAIL PROTECTED] wrote:
It appears that the issue
http://issues.apache.org/jira/browse/WICKET-606
that was fixed in beta2 is broken again in beta4. Basically TextFields
for
Strings (configured with the defaults) are always converting to empty
strings
The Wicket Web Beans project (wicketwebbeans) is active, but it has nothing
to do with the Web Beans JSR. Whatever name you choose is fine by me, but
you probably want to prevent confusion. I'd say having two projects or two
jars both with webbeans in the name would be confusing.
Is that JSR
+1 for wicket-candi !! ;-)
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
Wicket Web Beans 1.0-rc2 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
generated based on bean properties and certain conventions. If necessary,
the layout,
You need to check out the entire trunk, not just wicketwebbeans-examples.
The examples rely on the parent maven project.
When using the .war file, the URL you need to use is:
127.0.0.1:8080/wicketwebbeans-examples/WebBeans
See http://wicketwebbeans.sourceforge.net/wiki-html/RunningSamples.html
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
generated based on bean properties and certain conventions. If necessary,
the
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
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
In WWB, if you want the related bean to only show certain attributes, you
can put something like:
YourBean { ... props: name, -someOtherAttribute, ...; ... }
in your beanprops file. This will remove someOtherAttribute from your
view. Does that help?
-Dan
On Fri, Jun 13, 2008 at 6:02 AM,
26 matches
Mail list logo
