Unfortunately this is sent to the commits list which is publicly available.
Martijn
On Jan 8, 2008 8:15 PM, [EMAIL PROTECTED] wrote:
Page Edited : WICKEThttp://cwiki.apache.org/confluence/display/WICKET:
WicketAdminhttp://cwiki.apache.org/confluence/display/WICKET/WicketAdmin
Yes I saw that. I removed the page again.
On Jan 9, 2008 9:57 AM, Martijn Dashorst [EMAIL PROTECTED] wrote:
Unfortunately this is sent to the commits list which is publicly
available.
Martijn
On Jan 8, 2008 8:15 PM, [EMAIL PROTECTED] wrote:
Page Edited : WICKET
These were some changes we had made. I want to contribute them back to the
project. My comments are in bold.
mohan.shenoy wrote:
I have made some improvements in my working copy. I am attaching the diff
file.
I am looking forward to your questions and comments.
Thanks,
Mohan
I
hi
can I have commit access on wicket-contrib-javaee ?
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicket-contrib-javaee
Original author doesn't have time to work on it but there are some
important things that should be done like:
+ POM cleanup
+ it needs
We've tried annotations for lifecycle methods and that didn't work
out. But I think other parts of our API can benefit from annotations.
I suggest we take a look at annotations for:
* the mount with a page
*
Martijn
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket
Wicket currently provides RequestCycle#onRuntimeException with the
full exceptions, including the Wicket wrapped exceptions. Is this
something we should/could improve on?
For instance the thrown exception in this onclick handler:
add(new Link(foo) {
public void onClick() {
throw new
you mean @Mount(/foo) class MyPage extends WebPage {...}
then we have to scan the classpath for all classes that have that
annotation.
-igor
On Jan 9, 2008 2:53 PM, Martijn Dashorst [EMAIL PROTECTED] wrote:
We've tried annotations for lifecycle methods and that didn't work
out.
On Jan 10, 2008 12:06 AM, Igor Vaynberg [EMAIL PROTECTED] wrote:
you mean @Mount(/foo) class MyPage extends WebPage {...}
then we have to scan the classpath for all classes that have that
annotation.
Yep, though scanning classpath seems to be the rage currently.
Martijn
--
Buy
im not a big fan of scanning classpaths
-igor
On Jan 9, 2008 3:10 PM, Martijn Dashorst [EMAIL PROTECTED] wrote:
On Jan 10, 2008 12:06 AM, Igor Vaynberg [EMAIL PROTECTED] wrote:
you mean @Mount(/foo) class MyPage extends WebPage {...}
then we have to scan the classpath for all classes
On Jan 10, 2008 12:15 AM, Igor Vaynberg [EMAIL PROTECTED] wrote:
im not a big fan of scanning classpaths
Are you willing to share your concerns?
Martijn
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0 is released
Get it now:
I suggest we take a look at annotations for:
* the mount with a page
A disadvantage to doing that imho is that you'll have those
definitions scattered throughout. Right now we steer people to do it
in one place.
Eelco
On Thursday 10 January 2008 08:55:38 Eelco Hillenius wrote:
I suggest we take a look at annotations for:
* the mount with a page
I like it.
A disadvantage to doing that imho is that you'll have those
definitions scattered throughout. Right now we steer people to do it
in one place.
I
12 matches
Mail list logo
