Hi, You have your problem then :). As for my third question, you could have had a performance issue there as well. Imagine you have:
1 none scoped bean named "injected" 1 request scoped bean named "controller" called by your button and on which you inject the first bean. Now, imagine "injected" constructor does something really costly like multiple database calls or something, then calling the action on the "controller" bean will also be long for the first call for the actions to resolve in order will be to instanciate "controller" (fast), instanciate "injected" (slow), inject "injected" (fast) and finally call the action (fast). In the end, even if everything looks fast in your "controller" bean, it would still be slow because of "injected" instanciation. If you ever have such use case, try to make "injected" lifespan longer, like session or application. It might of course not always be possible though. Regards, ~ Simon On Tue, Sep 23, 2008 at 11:45 AM, Johannes Homuth < [EMAIL PROTECTED]> wrote: > Hello Simon, > > You are right, if I call the site again, it will be much faster. I think it > was the JSP Complation. I always redeployed my app after some changes and > thought that this JSP Site will be precompiled, but regarding your statement > i quess it will be compiled at first access. > > I just looked in the Internet and I quess I will have to use a > JSPPreCompileListener to solve this problem. > > Thx Simon!!! > > PS: Regarding your other suggestions.My bean is in request scope and yes I > inject some properties. Furthermore the method doesn't call a database, or > better to say, not yet. >
