That enables users to freely choose whether or not they want to use it.
+1 (if I get to vote)
-Nino
Eelco Hillenius wrote:
On Jan 10, 2008 9:32 AM, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
I think especially overriding setHeaders is not intuitive whereas an
annotation could really make
On Jan 10, 2008 9:32 AM, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> I think especially overriding setHeaders is not intuitive whereas an
> annotation could really make a difference in readability. But that is
> a different story.
>
> A simple 1 page guide showing the annotations and their uses i
On Jan 10, 2008 9:32 AM, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
>
> Hibernate/EJB3's annotations are just as hard to discover. But somehow
> folks do like them.
they like them because they are better then the alternative...
-igor
>
> Martijn
>
>
> On Jan 10, 2008 6:22 PM, Eelco Hillenius
I think especially overriding setHeaders is not intuitive whereas an
annotation could really make a difference in readability. But that is
a different story.
A simple 1 page guide showing the annotations and their uses is easy
enough to put on the web, in the distribution etc.
Hibernate/EJB3's an
> Playing the advocate of the devil: the thing with those is that it
> doesn't actually solve anything. I mean, you hardly decrease the lines
> of code you have to write to achieve something, annotations are
> arguably harder to discover than overridable methods, and we end up
> with having multipl
> - @Stateless - instead of overriding isStateless
> - @Headers - define headers specific for the page
Playing the advocate of the devil: the thing with those is that it
doesn't actually solve anything. I mean, you hardly decrease the lines
of code you have to write to achieve something, annotat
Possibilities:
- @Stateless - instead of overriding isStateless
- @Caching - how to cache the component's/page's markup
- @Headers - define headers specific for the page
Martijn
On Jan 10, 2008 5:43 PM, Ryan Sonnek <[EMAIL PROTECTED]> wrote:
> > Well, if you're going to do that, why not just
On Jan 10, 2008 5:32 PM, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> > Open questions:
> > - annotated page impossible?
> What do you mean?
Was: - annotated page impossible(?) to override/modify
Martijn
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0 is released
Get i
> Well, if you're going to do that, why not just mount the page in the
> application class and skip the annotation + registration altogether?
*IF* annotation support only includes mounting the url, i agree with
you. but if you start specifying url encoding strategies or other
useful page annotati
> 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() {
>
> One comment I have about classpath scanning is that *if* it turns out
> to be a nightmare, you could go the route of Hibernate where you have
> to register what annotated pages you want to support. ex:
Well, if you're going to do that, why not just mount the page in the
application class and s
> One comment I have about classpath scanning is that *if* it turns out
> to be a nightmare, you could go the route of Hibernate where you have
> to register what annotated pages you want to support. ex:
>
> public class MyWebApplication extends Application {
> public void init() {
> registe
> Pro's:
> - a long list of mounts becomes unmanagable
> - easy to add a mount: work on a page, slap on the annotation and you
> have your mount done
> - locality of the configuration
>
> Con's
> - distributed configuration, so hard to see the 'big picture' (though
> a mounts page listing all m
+1 for some R&D time. I think this could turn out to be *really* cool.
One comment I have about classpath scanning is that *if* it turns out
to be a nightmare, you could go the route of Hibernate where you have
to register what annotated pages you want to support. ex:
public class MyWebApplicat
+10 for exploring, you just never know what handy feature turns up:) I
meant to say that to in my previous mail.
Martijn Dashorst wrote:
Having the ability to specify the mount with the page instead of a
central location may be interesting. How is this different from
specifying to what table an
Having the ability to specify the mount with the page instead of a
central location may be interesting. How is this different from
specifying to what table an entity is retrieved from? I think having
all the things that relate to a specific page in one place is an
advantage.
I'm not sure what dese
I find the idea great. The other places where I've usage of this are xml
heavy frameworks like hibernate. You can then replace all the nasty xml
configurations with annotations.
However I don't see how that currently fit wicket? We just dont have a
lot of settings outside our javaclasses. Migh
@HomePage wuold not be very handy. Assume you have more than one page annotated
with @HomePage. Which should be the REAL homepage? Or should this result in an
error message during deployment?
Stefan
-Ursprüngliche Nachricht-
Von: Eduardo Ito [mailto:[EMAIL PROTECTED]
Gesendet: Donnerst
I agree...
What is the *advantage* of putting the mount definition in an annotation?
Following the same pattern, we would create a bunch of annotations
like @PageSettings, @HomePage, etc... argh!
On 1/10/08, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> > I suggest we take a look at annotations f
You're set to go.
Martijn
On Jan 10, 2008 10:59 PM, Maris Orbidans <[EMAIL PROTECTED]> wrote:
> it's marisorb
>
> Maris
>
> > Can't do anything without your sf.net id
> >
> > Martijn
> >
> > On Jan 10, 2008 6:51 AM, Maris Orbidans <[EMAIL PROTECTED]> wrote:
> >
> >> hi
> >>
> >> can I have commit
it's marisorb
Maris
Can't do anything without your sf.net id
Martijn
On Jan 10, 2008 6:51 AM, Maris Orbidans <[EMAIL PROTECTED]> wrote:
hi
can I have commit access on wicket-contrib-javaee ?
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicket-contrib-javaee
Origin
it's there
http://javaposse.com/index.php?post_id=295209
At 46:01
Martijn Dashorst <[EMAIL PROTECTED]> wrote: The podcast isn't yet available,
but apparently they'll mention Wicket
in the quick news...
Martijn
-- Forwarded message --
From: Google Alerts
Date: Jan 10, 2008 8:4
22 matches
Mail list logo
