tag:blogger.com,1999:blog-4110180.post4623628817673948819..comments2023-06-20T05:31:24.545-07:00Comments on Tapestry Central: Fighting with TomcatAnonymoushttp://www.blogger.com/profile/04486596490758986709noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-4110180.post-32084525673880990292007-02-22T09:10:00.000-08:002007-02-22T09:10:00.000-08:00Sorry Howard. It isn't Tomcat letting you down, i...Sorry Howard. It isn't Tomcat letting you down, it is Java.<BR/><BR/>Java very clearly doesn't support exploration of the package/class namespace. java.lang.Package has no tree-walking tools. java.lang.Class has nothing about the underlying .class file. There is nothing that requires .class files to be distinct filesystem resources at all. You could easily write a class loader on top of blobs in a database.<BR/><BR/>I wish that there <B>were</B> such an API and custom loaders just threw UnsupportedOperationException when the underlying fabric (e.g. remote codebases) failed to support it. But there isn't.<BR/><BR/>If I ever write one, I'll send it along.Michael Buckleyhttps://www.blogger.com/profile/11308089200065128056noreply@blogger.com