@In on SESSION scope component

[gersonk]

When the component has SESSION scope, the dependency injection will occur for every component invocation?

[gbc1]

Afaik stateless sessionbeans are held in a pool by applicationsserver. When invocation takes place seam intercepts activation and refreshes injected properties from contexts. But don't know if every @In property is always been injected new on every access or so.

Greetz GHad

[matt.drees]

Yes, no matter what the scope is, dependency injection occurs for every method invocation (except re-entrant calls).

[monkeyden]

Yes, we had some HUGE performance problems until we realized this. We have a relatively large form that was getting killed because of it.

[gbc1]

Well CR1 gave my huge performance boost and for my own inetrceptor I created a blacklist. This way the interceptor is able to forget not relevant methods and fields and only continues processing when it is necessary. Save a lot of runtime when the interceptor can concentrate on his issues when it is really needed. Or I may use beanutils... must go exploring..:-)

Greetz GHad

[gersonk]

thanks.

"monkeyden" wrote:
Yes, we had some HUGE performance problems until we realized this. We have a relatively large form that was getting killed because of it.

Interesting...
But even the form is so large, I suppose that Seam Interceptor basically just copy the object's reference to the attributes that have 'In' annotation. I can't see a huge cost of performance in that operation. (ok, the interceptor do much more than I described, but I can't see why a large form could slow down the performance in that way).
Could anyone explain it?

[monkeyden]

We're use i18n. In addition to the business processes of the actions, we were doing a lot of single message injection, using EL, which required parsing and evaluation of the expression and retrieval from the map.

Sure, a cursory assessment says bijection itself is not a problem, but when you have 25-30 value-binding methods called and 5-10 possible validation error messages bijected from your resource bundle, you take a vastly different approach to your implementation.