<div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Thu, Feb 23, 2017 at 11:27 PM Martin Kouba <<a href="mailto:mkouba@redhat.com">mkouba@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dne 23.2.2017 v 21:41 Laird Nelson napsal(a):<br class="gmail_msg">
> I haven't thought this through yet but I wonder if it would be helpful<br class="gmail_msg">
> to mark a Bean as synthetic or not—i.e. discovered by means of the<br class="gmail_msg">
> "normal" bean discovery process, or programmatically added by a portable<br class="gmail_msg">
> extension.<br class="gmail_msg">
<br class="gmail_msg">
I'm not sure it's worth specification. As Matej mentioned the<br class="gmail_msg">
ProcessSyntheticBean event should do the trick.<br class="gmail_msg"></blockquote><div><br></div><div>Yes; I just had completely forgotten about that.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> I was mentally working through what it might take to write up a sort of<br class="gmail_msg">
> CDI reporting mechanism—something that would report on what beans where<br class="gmail_msg">
> found, where they came from, what interceptors are enabled and why, etc.<br class="gmail_msg">
> etc. etc. and realized one axis of this would be whether a portable<br class="gmail_msg">
> extension was involved with certain beans or not.<br class="gmail_msg">
<br class="gmail_msg">
Something like Weld Probe [1], cdeye [2] or VisualEE [3]?<br class="gmail_msg"></blockquote><div><br></div><div>Yes (thanks for the pointers; only knew about two of them), but much simpler and limited in scope.</div><div><br></div><div>Best,</div><div>Laird</div></div></div>