<div class="gmail_quote">On Mon, Feb 7, 2011 at 14:56, José Rodolfo Carrijo de Freitas <span dir="ltr"><<a href="mailto:jose.freitas@softplan.com.br">jose.freitas@softplan.com.br</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div lang="PT-BR" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">It
Looks really nice!</span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"> </span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">If
I may suggest something, maybe we can add the possibility to use just <b>“.send()”</b>
( keeping the send(session) method ).</span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">If
there’s no specific session argument, the module could handle the
injection within itself.</span></p></div></div></blockquote><div><br></div><div>Yep, Emmanuel mentioned that as well. And I'll second both of you :)</div><div><br></div><div>Even if you use send(), you would still have flexibility in how the mail session is picked, because you could provide an alternative producer to create your own custom session. All that matters is that Seam Mail references a bean with type Session. So that version of send() will likely be preferred.</div>
<div><br></div><div>-Dan</div><div><br></div><div>-- </div></div><div>Dan Allen</div>Principal Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><div><a href="http://www.google.com/profiles/dan.j.allen#about" target="_blank">http://www.google.com/profiles/dan.j.allen#about</a><br>
<a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br></div><br>