At this point, I think that may actually be a good option. I can't get forge to start up in under 8 seconds anymore. I'm all for doing this I suppose, though it will be a bit of a departure from the current functionality. I like the auto-pickup, but this performance is pretty attrocious :(<br>
<br><div class="gmail_quote">On Sat, Jul 9, 2011 at 8:40 AM, Mark Struberg <span dir="ltr"><<a href="mailto:struberg@yahoo.de">struberg@yahoo.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Folks, what if we step back and fix the CORE of this disaster?<br>
<br>
Lets not pickup non CDI scope annotated beans as @Dependent automatically anymore!<br>
<br>
We could automatically enable this feature if we detect a version="1.1" in beans.xml. This way we can keep backward compatibility<br>
<br>
LieGrue,<br>
strub<br>
<br>
--- On Fri, 7/8/11, Dan Allen <<a href="mailto:dan.j.allen@gmail.com">dan.j.allen@gmail.com</a>> wrote:<br>
<br>
From: Dan Allen <<a href="mailto:dan.j.allen@gmail.com">dan.j.allen@gmail.com</a>><br>
Subject: Re: [seam-dev] Seam Startup Performance<br>
To: "Stuart Douglas" <<a href="mailto:stuart.w.douglas@gmail.com">stuart.w.douglas@gmail.com</a>><br>
Cc: "Seam Dev List" <<a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a>><br>
Date: Friday, July 8, 2011, 11:45 PM<br>
<div class="im"><br>
On Fri, Jul 8, 2011 at 19:27, Stuart Douglas <<a href="mailto:stuart.w.douglas@gmail.com">stuart.w.douglas@gmail.com</a>> wrote:<br>
<br>
<br>
Hi Guys,<br>
<br>
<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>
<br>
<br>
<br>
<br>
It occurred to me that we can get around this by using a beans.xml that includes welds <scan> extension in beans.xml to prevent uneeded beans being registered we could significantly improve the performance and memory usage of Seam 3 apps.<br>
<br>
<br>
<br>
Now that the ridiculous visibility and extensions in non-bean archive problems are resolved, I'm in favor of switching back to registering beans manually rather than using beans.xml. That seems like a performance enhancement that's portable, so that we don't suck if Weld isn't the provider.<br>
<br>
<br>
But I agree we should do one of the two options. We'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.<br>
<br>
<br>
-Dan<br>
--<br>
</div>Dan AllenPrincipal Software Engineer, Red Hat | Author of Seam in Action<br>
<div class="im">Registered Linux User #231597<br>
<br>
<a href="http://www.google.com/profiles/dan.j.allen#about" target="_blank">http://www.google.com/profiles/dan.j.allen#about</a><br>
<br>
<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>
<br>
<br>
<br>
</div>-----Inline Attachment Follows-----<br>
<div><div></div><div class="h5"><br>
_______________________________________________<br>
seam-dev mailing list<br>
<a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
<br>
<br>
_______________________________________________<br>
seam-dev mailing list<br>
<a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.com">http://ocpsoft.com</a><br><a href="http://scrumshark.com">http://scrumshark.com</a><br>"Keep it Simple"<br>