maybe we can provide a soft application-level context that modules can register things under, or some more typesafe module system.
we havent seen a lot of this happening and so coming up with a good solution is difficult. pretty much the only usecase we have is what you stumbled upon, intermixing spring and auth frameworks.
what do others think?
-Igor
On 6/7/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]
> wrote:
Hi all,
i started to learn about wicket. But i get confused, as more as i read.
Simplicity is wickets great promice. The approach is great: Java and Html,
no XML, noJSP, that sounds fantastic, but now i have to build up knowlede
'from the ground' around wickets architecture first. However, i will not
give up, there is no alternative and as far as i can, i will help, at least
with my humble comments. :-)
But now to my actual question; At the auth module, the application is used
to act as a single point of initialization, inherit by
AuthenticationApplication or something. Combining Wicket with Spring, again
the application is used to inherit now from the DataApplication.
I expected to code nothing new but rather just to use modules, but it
seems, that i have to. So, how can i combine at least these two aspects
(Databinding via Spring and authentication) as easy as possible?
And another question: Is it planned to deal with the portal spec? Or: How
can i control the application considering the users role?
Thx in advance!
Cheers, Peter
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
_______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
