i was referring to an implementation of iwebapplicationfactory not the springpagefactory. there are a lot of issues with page-level injection that arise from the fact that wicket serializes pages into session and so how do those pages get their dependencies injected back when they are deserialized? there have been some attempts to do it with spring's aop, but personally i do not like that approach. maybe there is a better way. when i have time i will look into it more, if you have any ideas i would love to hear them.

btw, for an implementation of a springware iwebapplicationfactory see wicket-phonebook in wicket-stuff.

-Igor


On 11/5/05, Ryan Sonnek <[EMAIL PROTECTED]> wrote:
+1 for improving spring web page factory.  spring is becoming one of
the most widely used open source projects, and right now it's a
considerable amount of work, and confusion, to use spring with wicket.
I *strongly* believe that people that like spring will turn to other
frameworks like webwork or spring-mvc if wicket doesn't have better
integration.

On 11/5/05, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> i agree, i dont really like the model level integration in the wicket-stuff
> spring project either.
>
>  i think as far as standardization we can only go as far as provide an
> implementation of IWebApplicationFactory that pulls out the
> wicketapplication object from the spring webapplication context.
>
>  page level integration would be nice, but it is tricky due to serialization
> issues. maybe when we elegantly crack that nut we can make it a standard and
> supported way.
>
>  -Igor
>
>
>
> On 11/4/05, Dan Gould <[EMAIL PROTECTED]> wrote:
> > Igor Vaynberg wrote:
> > > what do you mean by cleaner spring integration?
> > > -Igor
> >
> > To be honest, I'm not sure.  Right now, I use "Model Level" integration
> > following
> >
> http://www.wicket-wiki.org.uk/wiki/index.php/SpringIntegration
> >
> > though I've also tried "Page Level Integration".  It works perfectly well,
> > but there seems to be a bunch of boilerplate that could be removed, and
> > the whole getContext().getBean() aspect seems to me to be un-Spring-like.
> > I guess I'm thinking that injection would be nicer than a service locator
> > pattern.
> >
> > If nothing else, I suppose I'm looking for one of those methods to become
> > the "standard" that's used in examples.
> >
> > [That said, OpenSessionInViewInterceptor makes handling database sessions
> > really nice.]
> >
> > Sorry I don't know exactly what I want, but hopefully others do.
> >
> > Best,
> > Dan
> >
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by:
> > Tame your development challenges with Apache's Geronimo App Server.
> Download
> > it for free - -and be entered to win a 42" plasma tv or your very own
> > Sony(tm)PSP.  Click here to play:
> http://sourceforge.net/geronimo.php
> > _______________________________________________
> > Wicket-develop mailing list
> > [email protected]
> >
> https://lists.sourceforge.net/lists/listinfo/wicket-develop
> >
>
>


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop

Reply via email to