Is there any reason seam-bridge-api and seam-webbeans-bridge shouldn't move to
webbeans-extensions? I have this jira issue:
to allow the webbeans wicket support to work with any jsr-299 impl,
and part of making that work is providing a way for the wicket
extension to grab the current manager instance. It seems like this
is useful independent of seam.
Scalable Web Application Development