On Fri, Jul 8, 2011 at 19:27, Stuart Douglas <span dir="ltr">&lt;<a href="mailto:stuart.w.douglas@gmail.com">stuart.w.douglas@gmail.com</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

Hi Guys,<br>
<br>
I was just looking at the startup performance of the Seam 3 booking example on AS7, and I noticed that because the Seam 2 archives that it deploys are bean archives, it actually wastes quite a lot of time on startup registering Seam 3 classes as CDI beans that are never used.<br>


<br>
It occurred to me that we can get around this by using a beans.xml that includes welds &lt;scan&gt; extension in beans.xml to prevent uneeded beans being registered we could significantly improve the performance and memory usage of Seam 3 apps.<br>

</blockquote><div><br></div><div>Now that the ridiculous visibility and extensions in non-bean archive problems are resolved, I&#39;m in favor of switching back to registering beans manually rather than using beans.xml. That seems like a performance enhancement that&#39;s portable, so that we don&#39;t suck if Weld isn&#39;t the provider.</div>

<div><br></div><div>But I agree we should do one of the two options. We&#39;ll be moving tests around in Seam to align the setup, so it seems like a good time to run tests with the updated bean registration strategy.</div>

<div><br></div><div>-Dan</div><div><br></div></div>-- <br><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>