"epbernard" wrote : | I think it has been discussed previously in this thread. | It's been discusses many times, but never really resolved. ;-) This wasn't a critical issue before, since our CLs were URLCLs, and we were able to hack around it. But it is critical now, after the change to new classloader. "epbernard" wrote : | There are 2 problems: | - the spec ask for a URL, so URL it has to be to plug any JPA implementation | URLs are not the problem. They are transparently handled by the Handlers via VirtualFileURLConnection. "epbernard" wrote : | - writing an resource scan and context discovery is certainly possible but will require me a lot of work. | Perhaps an initial impl could just forget about the URLCL. "epbernard" wrote : | Before we do that, I need a) time b) a proof that it will speed up things significantly e.g. The proof would be that in the case of Seam app, you wouldn't need to scan things 3 times: Seam, EJBs, HEN. The EJB deployer would do that for you, and the frameworks would just aks the deployer for already 'cached' info. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4120446#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...