"adrian(a)jboss.org" wrote : "max.andersen(a)jboss.com" wrote : ...but why
is this concern of where to get resources from leaked out via the urls passed down to
hibernate via the urls it gets ? Can't we avoid that somehow?
|
| I don't understand your question? You need some identifier.
| JavaEE generally uses URLs (but they are not navigable
| there is no generic getChildURLs()).
|
| Currently hibernate gets the top level url and barfs because it only knows
| how to navigate file:, jar:
| There is no way to make it understand anything else.
|
Correct, I think Max's train of thoughts goes down to: could the VFS implement
openStream() is such a way that it would look like a JAR stream? When I wrote the visitor,
this was really the "common interface" I expected URLs I interact with to
implement.
"adrian(a)jboss.org" wrote : We're discussing how to go beyond these for
reasons of optimization
| and ease of use/development.
|
| If you want to avoid the problem then we say you always have to package
| as a jar or exploded archive and we will always scan everything (multiple times :-)
|
I understand that scanning multiple time is stupid (though some hard figures would be
better :o) ).
But how does the VFS provide some ease of use / dev? I can't find a clear benefit for
Joe Pack (though I imagine Max like the concept when integrating into Eclipse).
Exposing an interface is possible but is a decent amount of work. I would like to just the
urgency / necessity / usefulness before going that road :)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109071#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...