I'm wondering, does every JBossAS deployer does scan the endpoint ?

Or is there some shared deployer which scans an endpoints for all the annotations and creates some per-endpoint annotations pools, and then concrete deployers check the annotations pools only ?

Hi, >> I'm wondering, does every JBossAS deployer does scan the endpoint ? > Endpoint, as in WS endpoint? > More likely you mean endpoind == deployment (which also includes > subdeployments)? Sorry, my terminology was wrong. What happened was that I deployed a war into JBossHome/server/default/deploy and it failed with the expected ClassNotFoundException (due to one of the dependencies required by that war still missing), and I just got surprised the failure came from the RestEasy (possibly JBoss Integration related) code doing the annotations scanning >> Or is there some shared deployer which scans an endpoints for all > the annotations and creates some per-endpoint annotations pools, and > then concrete deployers check the annotations pools only ? > > Every deployer checks every depoyment (and subdeployment, ...). > But the idea is to short circuit asap if the deployment is not > relevant to the deployer. > > Here is my DZone article on VDF / deployers: > * > http://java.dzone.com/articles/jboss-microcontainer-virtual-deployment-fr... > Which should give you a quick overview of things. > > More details on (annotation) scanning can be found here: > * http://java.dzone.com/articles/jboss-microcontainer-scanning > Thanks - this is helpful Sergey > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

> I'm not sure if our scanning framework uses reflection or Javassist. If > it uses reflection, I could see CFE errors happening. It uses JBoss Reflect. And currently Reflect uses JDK Introspection for reflection. If for some reason you would still need lazy class loading, you can easily switch Reflect to use Javassist. But this would have an impact on boot time, as Reflect Introspection impl is faster then Reflect Javassist impl.

You probably use JDK Introspection for performance? Beyond possible CFE problems, this is probably also a big permgen memory consumption issue, especially with deployments with big third-party dependencies, no? Wasn't somebody working on an optimized javassist-like approach?

We tried both javassist and an even more optimized version using ASM. Unfortunately none of these worked out as planned and slow down boot time, so they are put on hold at the moment. On 19 Jul 2010, at 09:57, Andrew Dinn wrote: > On 07/16/2010 04:29 PM, Bill Burke wrote: > >> You probably use JDK Introspection for performance? Beyond possible CFE >> problems, this is probably also a big permgen memory consumption issue, >> especially with deployments with big third-party dependencies, no? >> Wasn't somebody working on an optimized javassist-like approach? > > I think Kabir has implemented an alternative approach based on Javassist. If I remember correctly (increasingly unlikely these days but you never know) it is faster. Perhaps he can comment. > > regards, > > > Andrew Dinn > -----------