But since I'm currently learning, I can't help wondering at each step
where the data gets stored magically. Likely that will go away once I
know my way around Wicket. It's also not a complaint, just part of
getting to know the best way of doing things.
I think it's a very good idea you have
If you're interested, a contribution for the address book example with
exPOJO/ JPOX would be more than welcome.
Definitely, not a problem. When do you need it by?
Whenever you feel like it.
Where can I find the spec for the address book app?
No spec, only code :)
To: users@wicket.apache.org
Subject: Re: wicket vs tapestry ?
Hi,
2) I like the back button support. My thinking is that extending Wicket's
AJAX integration to also support the back button (somehow) is a must.
Virtually everyone who uses Wicket will use it's AJAX functionality. Almost
all
On 8/23/07, William Hoover [EMAIL PROTECTED] wrote:
Possible starting point for a client solution for back button
detection/support:
http://www.onjava.com/pub/a/onjava/2005/10/26/ajax-handling-bookmarks-and-back-button.html?page=1
Thanks for suggesting. We have discussed that and other
On 8/22/07, Alex Shneyderman [EMAIL PROTECTED] wrote:
I just started to look for a component based framework. I came across
both tapestry and wicket (and it would be hard not to as you guys
share the same host) but I kind of fail to see what the differences
are?
From my limited experiments
Hi
I have been using wicket for quite some time now. Prior to this I worked
on tapestry for a short time . (In fact i implemented the same pages
which i did in tapestry in wicket also)
I may not be able to give you the right answer but i can definitely say this
the learning curve in tapestry
i think igor has some more info...
On 8/22/07, Alex Shneyderman [EMAIL PROTECTED] wrote:
I just started to look for a component based framework. I came across
both tapestry and wicket (and it would be hard not to as you guys
share the same host) but I kind of fail to see what the differences
Eelco Hillenius wrote:
You can download the first chapter of Wicket In Action for free here:
http://manning.com/dashorst/ and some chapters of Tapestry In Action
Wow, Wicket In Action, we're all were waiting for it :-)
Is this early access edition mature enough to buy or it's better to
@wicket.apache.org
Subject: Re: wicket vs tapestry ?
Eelco Hillenius wrote:
You can download the first chapter of Wicket In Action for free
here:
http://manning.com/dashorst/ and some chapters of Tapestry In
Action
Wow, Wicket In Action, we're all were waiting for it :-)
Is this early
On 8/22/07, Chris Colman [EMAIL PROTECTED] wrote:
Hi Eelco,
I saw you mention Hibernate in the intro but I've been using JPOX with
great success with Wicket also. You might want to mention that in the
book or new comers might think Wicket is a Hibernate only framework.
I use JPOX through
You mean the wicket-phonebook?
Martijn
--
Wicket joins the Apache Software Foundation as Apache Wicket
Apache Wicket 1.3.0-beta2 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta2/
-
To
On 8/22/07, Martijn Dashorst [EMAIL PROTECTED] wrote:
You mean the wicket-phonebook?
Yeah.
Eelco
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
2) I like the back button support. My thinking is that extending Wicket's
AJAX integration to also support the back button (somehow) is a must.
Virtually everyone who uses Wicket will use it's AJAX functionality. Almost
all of these will need solve this problem. Sure would be nice if
You can download the first chapter of Wicket In Action for free here:
http://manning.com/dashorst/ and some chapters of Tapestry In Action
here: http://manning.com/lewisship/
Actually, Tapestry in Action is pretty old and covers only Tapestry 3. I
would advice downloading chapters 1-4 of
Unfortunately, that's an assumption that many people make. But say
that you're not worried about optimizing and one session means about
100kb (on the high side, as with optimizing in my experience you
should be able to bring that to 15-30kb)... That means you can support
10,000 concurrent
15 matches
Mail list logo
