On Fri, Jun 12, 2009 at 6:10 AM, Pete Muir <email@example.com>
Stuart, I agree, this is long overdue.
I took a look at your patch, there seems to be a number of problems (System.out.println, changing of SPIs with no changes made to the JBoss5 int project at least), and it is essentially a workaround for a mistake in the underlying architecture, as a result I would prefer to defer this to 299, which does correctly scope all components to the relevant JEE module.
Hmm, I was thinking this was going to get into 2.2 as well...or at least 2.2.1. I know that solving problems like this one is much easier and cleaner w/ 299 given that we have a chance to start over, but I worry that there are enough folks that really need this capability w/o refactoring the rest of their code. Even with 299 in place, if there is any Seam 2 code, users are still going to have the same issue (assuming that this problem is baggage that Seam 2 brings with it).
Stuart, would you be willing to work through this piecemeal? That will make success much more likely. And this really would be huge for Seam 2 if we could get it fixed.