<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"><br>
> WeldContainer weld = new Weld().initialize();<br>
> weld.instance().select(Foo.class).get();<br>
<br>
</div>Yes, this seems sensible to me, as it will allow us to provide flexibility with the configuration in the future.</blockquote><div><br>Emmanuel, master of fluent APIs, has made an important point that we should keep in mind when designing a sequential call chain. Think twice before returning "this" and think if there is a more specific type that you can return that narrows the options based on where you are in the sequence. That way, you prevent being able to invoke methods out of sequence.<br>
<br>You can now prevent:<br><br>new Weld().event()<br><br>Returning a more specific type is also self documenting.<br><br>-Dan</div></div><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>
Registered Linux User #231597<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://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>