re application subclasses

well, maybe we do what i did in wicket-spring, instead of subclassing webapplication create a class that holds the functionality, and store it in the application's metadata where other who need it can get to it.

i dont see a reason to have a formal module system yet (ala behaviors) because the application itself doesnt provide any functionality really and is not a target of any events that the modules might be interested in.

-Igor


On 9/21/06, Nathan Hamblen <[EMAIL PROTECTED]> wrote:
The colliding Application subclass problem is the reason I made
AuthDataApplication, which copies the good stuff from
AuthenticatedWebApplication. It's used in this example:
http://databinder.net/recipe-book.html

But yes it's a problem. I was waiting for some guidance from
wicket-contrib (since that's where the idea of subclassing
WebApplication came to me from) but as it keeps coming up I'll see what
I can do to make it easier to use Databinder with an independent
Application class.

Nathan

Ayodeji Aladejebi wrote:
>
> Okay I know of all the contrib projects, databinder, hibernate stuffs
> etc, I have used databinder and its lovely but I think for some reason,
> database in wicket needs to be sort of easier to put up to encourage
> faster adaptation. Come to think about it, presently most of the present
> solutions around database in Wicket wraps around Hibernate and a
> beginner who is not familair with hibernate may get stuck. Some
> developers still tend to love thier SQL thing compared to ORM and in
> some cases, you want to do direct SQL cuz hibernate3.jar is some size
> you may not need to include in your portable web application. And
> believe me, i believe more ppl learn SQL more than they learn ORM in Schools
>
> Yesterday, I was tryin to use Dababinder or wicket-contrib-dababase but
> at the same time i was using the wicket-auth framework and all these
> contibs enforce that you extend XXXApplication in your Application Class
> which means you cannot directly use Contrib projects e.g
> wicket-contrib-database and also Wicket-auth. There should be a more
> elegant way to use multiple contrib projects without this Inheritance
> lock jam.
>
> Now most web applications need authentication and also need database
> which is why i believe wicket shoud somehow integrate some DAO scheme
> into wicket where all we do is set connection properties and from
> Components, you can fly CRUD.
>
> Well i know there must be some good reasons to exclude this from wicket
> but what will be the most elegant way to do CRUD in wicket?  where
> should I store my Connection? Session or Application Class. Should I
> create a parent WebPage with all the SQL stuffs and then make other CRUD
> pages extend it. a hundred ways to do this but which way is more elegant?
>
> Thanks Wicket dads
>


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to