anonymous wrote : | Re-read the JNDI example. ;-) | Or how else are you gonna make sure you don't miss a potential dependency resolving bean, | if you don't check them all? |
One idea would be to process the dependencies statically via an installation/configuration step that generates initialization code. This could be done via the MC compiler (MCC or maybe YAMCC). I know that we don't have this now but I like the general idea of pre-compiling/caching what ever stuff makes sense to improve performance. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244091#4244091 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244091 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
