On Fri, May 22, 2009 at 5:50 PM, Clint Popetz <cpopetz@gmail.com> wrote:

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.

I think we are engaging in a struggle over ownership of features and defining boundaries between Seam and WB.

In my definition, Seam is the universal middleware stack at Red Hat which is most definitely independent of JSR-299 implementation. Therefore, it's my position that anything that "extends" 299 towards "rich web" should be a module of Seam. Extensions which don't go in that direction, such as the Java SE support, are a better fit as a webbeans extension. Furthermore, I don't think you should feel like you "have to depend on Seam" because it isn't going to be like Seam 2 where it is all or nothing. Modules are starkely independent and can be seen as a lose collection of extensions.

Perhaps others will disagree with my definition, or think it too liberal, but if we don't define where Seam begins, then you could easily rationalize all modules of Seam be extensions of Web Beans...I will admit though that the bridge is a gray area in that it could go either way.


Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action


NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters.  Please don't hesitate to resend a message if
you feel that it did not reach my attention.