Seam 2 did injection/outjection every time a method was called, Seam 3 (and 299) does resolving at boot time and wiring at bean creation time. This can add up since e.g. JSF can end up calling stuff multiple times.
Perhaps Pete or Dan who knows the Seam 2 arch better can throw in a brief summary?
- less use of interceptors
- upfront resolution of dependencies
- better use of reflection (caching, and possible delegation to container)
- delegation of services to container
are the key ones.
Hey Pete, where can I find this excellent presentation?