<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
I really see this as a module. It's no different than our current spring (and now guice) integration in that sense. We could have an "ioc" common module and then have modules that build on that. But in general it is IoC (or really DI) related.<br>
</blockquote>
<br></div>
IOC was a bad name for that module originally, lets not repeat that mistake.</blockquote><div><br>What about DI, or is that too general? I guess the first question to answer is what is the nature of these integrations. The JBoss AS team has probably thought about this terminology so we should see what they have to say about the name. Obviously, each integration would be named after the framework, but if there were shared code what would it be called? Not a question we have to answer right away.<br>
<br>-Dan<br></div></div><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>
<a href="http://in.relation.to/Bloggers/Dan">http://in.relation.to/Bloggers/Dan</a><br><br>NOTE: While I make a strong effort to keep up with my email on a daily<br>basis, personal or other work matters can sometimes keep me away<br>
from my email. If you contact me, but don't hear back for more than a week,<br>it is very likely that I am excessively backlogged or the message was<br>caught in the spam filters. Please don't hesitate to resend a message if<br>
you feel that it did not reach my attention.<br>