"steve.ebersole(a)jboss.com" wrote :
| You can, sure. But what about other app severs/environments... If the
URLConnection/ContentHandler approach is more "correct" and the vfs stuff will
really handle it correctly, then whats the issue with using that? Seems like a more
universally applicable solution. But of course, I'm a dolt (^^) so please enlighten
me ;)
Where in the URL api does it have a listChildren(), etc.? :-)
You have to use a specific api, e.g. java.io.File or java.util.jar.JarFile
before you can look at structure.
This adhoc processing (usually done wrong in multiple places :-) is one of
the reasons we introduced the VFS, so we can do it correctly in one place
and extend it.
All I'm asking is for a way to plugin where currently hibernate takes a
non-overriable decision. If other appservers want to plugin as well
then ok. Even something as simple as:
| package org.hiberante.vfs
|
| public interface URLLister
| {
| URL[] getChildren(URL parent);
| }
|
would mean we could do:
-Dorg.hibnerate.vfs.URLLister.vfs=org.jboss.hibernate.vfs.VFSURLLister
i.e. a system/hibernate property org.hiberate.vfs.URLLister.{protocol}
I'm sure you can come up with something better :-)
I'd prefer something at a higher level. Mainly because
we are already scanning classes for annotations for other reasons so we
can optimize your search for those that are marked @Entity or whatever
filtering you need.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108965#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...