Tom, I don't follow you with the global setting. I still think it should be able to be configured on the node itself.
Imo, there are cases in which you want the mail directly: eg for handling an exception or a timer times out when waiting for an external system -> send an email to the system admin directly.
In this case, scheduling it and waiting for the jobExecutor will cause a serious and unacceptable slow-down ... unless the jobExecutor is polling all the time (which is not good for performance).
For normal mails, I agree they are to be scheduled.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223887#4223887
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223887
"jason.greene(a)jboss.com" wrote :
| So why does it need to scan everything, if the MDR already knows how to fetch it lazily?
Fetch it how or what?
For each instance and its component (= member) the metadata can be different.
So, you need to explicitly ask for every component's metadata via its signature.
And afaik that's the only way you can get per instance metadata,
but you can prove me wrong. ;-)
WRT to over-abstracted crap ;-)
having a way to add annotations via xml is a nice feature (OK, Emmanuel would disagree :-)),
and @JMX is a perfect example of that.
Hence when we make an annotation lookup,
it should be done properly, taking those per instance annotations into an account.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223869#4223869
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223869
"jason.greene(a)jboss.com" wrote : Now for an actual productive comment :) Is there any reason why the MDR has to eager allocate everything about every element of of every scanned class in memory like that? Any reason it can't just represent metadata as a series of overrides + lazily discovered / proxied calls to reflection data.
Ah looking at the code, it seems this is basically what the MDR does, the problem seems to be that the API was designed for fetching specific elements, and depending on the usage, each access could be expensive (especially the reflection loader).
So why does it need to scan everything, if the MDR already knows how to fetch it lazily?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223843#4223843
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223843