Any chance you'd have time to add a V2.0 update to that effect here
- http://www.wicket-wiki.org.uk/wiki/index.php/Spring :-)
/Gwyn
On 09/08/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
i have recently deprecated springannotwebapp so this no longer should be a
problem. now to get spring
On 8/9/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
i have recently deprecated springannotwebapp so this no longer should be a
problem. now to get spring injection going you do this:
class myapplication extends webapplication {
init() {
addComponentInstantiationListener(new
it will be in both 1.2.2 and 2.0its in svn right now...still working on support for portlets but webapps are ready to go.-IgorOn 8/9/06, Mats Norén
[EMAIL PROTECTED] wrote:On 8/9/06, Igor Vaynberg
[EMAIL PROTECTED] wrote: i have recently deprecated springannotwebapp so this no longer should be a
updated-IgorOn 8/9/06, Gwyn Evans [EMAIL PROTECTED] wrote:
Any chance you'd have time to add a V2.0 update to that effect here- http://www.wicket-wiki.org.uk/wiki/index.php/Spring :-)/Gwyn
On 09/08/06, Igor Vaynberg [EMAIL PROTECTED] wrote: i have recently deprecated springannotwebapp so this no
Thanks!
On 09/08/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
updated
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
i have recently deprecated springannotwebapp so this no longer should be a problem. now to get spring injection going you do this:class myapplication extends webapplication { init() { addComponentInstantiationListener(new SpringComponentInjector(this));
}}thats it, no need for extending any
Has there been any progress in merging AuthenticatedWebApplication and
the spring-stuff lately or is there a best praktice out there
somewhere?
Best regards Mats
On 6/8/06, Martijn Dashorst [EMAIL PROTECTED] wrote:
The problem is that the wicket-auth-roles package assumes you subclass
The problem is that the wicket-auth-roles package assumes you subclass AuthenticatedWebApplication as your application class. If you want to reuse that, you'll have to subclass the AuthenticatedWebApplication and the AuthenticatedSession.
No spring can fix that.MartijnOn 6/8/06, Mark Derricutt
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
I don't like those 'convenience' application classes. We should get
rid of them and replace them with a better pattern. Not sure what that
would look like at this time.
Eelco
On 6/7/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
this is a problem that we are aware of. we will have to modularize
On 6/7/06, Martijn Dashorst [EMAIL PROTECTED] wrote:
I suggest (tried and tested at my company) to use the Auth application as your base class and merge the spring related stuff into your subclass. The spring integration is agnostic for sessions and such, so you'll be up and running much quicker.
11 matches
Mail list logo
