When dealing with VFS URLs pointing to some nested resources, things get horribly slow due to huge VirtualFileURLConnection usage. Here is where things are explained a bit more on real Seam example: - http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184779#... The possible solutions I see. 1) try to impl those Seam use cases directly on VFS - same way we do it for Deployment and CL Q1: can we really do it for all cases? Q2: what about other non-integrated frameworks in JBoss5? 2) change how we handle VFS URLs - same way we do it in pre-JBoss5 Q1: what's the reason we don't return VFS URLs with temp paths? 3) implement some simple VFS caching Q1: use real cache, e.g. LRU, or is SoftRef enough? Q2: we need to cache intermediate paths - getting different resources from same parent faster (this requires VFURLConnection impl change) Q3: transparent AOP usage - caching is an aspect? Any other ideas? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184788#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...