Yes, Spring MVC, I also like use some Spring components (though I don't like
xml-based dep injection).
1) Borders and panel - yes, that seems to do what
2) ... well, I usually appreciate a webpage to AT LEAST put the problem fields
on emphasis, messages on the bottom confuse me, specially if they have more
than 5 or 6 fields. But I guess it's a matter of personal opinion. Still,
anyone knows the answer for this one?
3) The base class works too. The only drawback is that it does not garantee
that a novice programmer won't forget to extend that class and thus break
security.
Thanks for the answers, I think I can try it out now!
[]s Gus
---------- Início da mensagem original -----------
De: [EMAIL PROTECTED]
Para: [email protected]
Cc:
Data: Thu, 16 Jun 2005 15:12:48 -0700
Assunto: Re: [Wicket-user] Starting in Wicket
> Well, first off, I assume you mean Spring MVC, since that would be the
> only competitor with Wicket. And you're right, Spring MVC is nice, but
> it's still a model 2 framework. It was just added to the project as a
> kind of default web tier framework. I use Spring with Wicket for the
> web tier; they are a great pair that way.
>
> 1. Check out the border and panel components. They do exactly what
> you're looking for. The examples use them extensively.
>
> 2. This one I don't know about since I hate webpages that do that. If
> there is a way to do this, I would like to know about it though.
>
> 3. Just extend a common Page class that does whatever you need in the
> constructor. Alternatively, you could create a custom IPageFactory
> implementation that would execute whatever code you wanted before a
> page was created. Take a look at Page.checkAccess for your specific
> requirement. It makes security a breeze.
>
> On 6/16/05, Gustavo Hexsel <[EMAIL PROTECTED]> wrote:
> > Hi folks,
> >
> > I'm evaluating Wicket as a replacement for some of our web code. I've
> > checked out Spring and found out that besides the learning curve being very
> > high for anything but trivial tasks, it didn't save as much coding as I
> > expected...
> >
> > So I've realized that some things that frameworks don't show you in
> > tutorials are usually the hard ones. I've been trying to find out how to
> > do some things in Wicket, but couldn't find anywhere in the docs or
> > examples (I wonder if I looked in the right places)
> >
> > - what's the preferred way of nesting web pages? Like adding a default
> > menu, a header, etc. Would you <@page import> it?
> > - how do you provide per-field feedback? The feedback-panel component just
> > accumulates all fields in a single component.
> > - is there a way of forcing a filter before all pages (for instance, to
> > check if a login is present in the session) without having to edit all
> > pages? Or should I use a filter as in the Servlet API?
> >
> > Thanks a lot!
> >
> > []s Gus
__________________________________________________________________________
UOL Fone: Fale com o Brasil e o Mundo com até 90% de economia.
http://www.uol.com.br/fone
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
