Re: AW: Re: [Wicket-user] Page lifecycle notification

[Eduardo Rocha]

Using a custom page factory to load Spring dependencies is discussed in the Wiki, and the issue about serialization/deserialization is what made some people take alternatives, like Service Locators. I went a little further and based on Eelco's idea (some old discussion about Spring), I've implemented an aspect that injects the dependencies before a constructor is called, and after an object gets deserialized, using annotation to know what is the dependency. Maybe I can put somewhere if someone's is interested. Any other way to do Spring integration concerning serialization/deserialization and not using static Service Locators?

2005/10/7, Eelco Hillenius <[EMAIL PROTECTED]>:

That's the pattern I use too. But... it's not the pattern Sven asked
for/ refered to, so I was trying to think of options that satisfy his
need.

I think - when reading what an 'application transation' means in the
article - using statefull session beans is the cleanest approach then,
as the Wicket UI is too detached (at least it should be) from the
business layer for such an approach.

Eelco


On 10/7/05, Gili < [EMAIL PROTECTED]> wrote:
>
>         Hmm, excuse me... but it seems to be that you could accomplish exactly
> what you are asking for by hooking beginRequest(), endRequest() methods
> to open and close your Hibernate session. Hibernate conventions
> discourage the use of long-term sessions so this is actually what you
> should be doing. Opening a new Session is dirt cheap.
>
> Gili
>


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user