DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15279>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15279 WriteableSource doesn't work with context: URLs ------- Additional Comments From [EMAIL PROTECTED] 2002-12-11 17:10 ------- The problem comes from the order in which SourceFactories and URLFactories are used. The SourceResolver first checks if a SourceFactory exists for the requested protocol. If none exists, then it checks if a URLFactory handles the protocol, uses it to get a standard java.net.URL and builds an URLSource, which isn't writeable. The writeable "file:" source is handled by a SourceFactory whereas the "context:" protocol is handled by a URLFactory. This means that a "context:" is translated to a "file:" java.net.URL by the ContextURLFactory, and that an URLSource is built (not a WriteableFileSource). Hence this bug. Changing the lookup order won't work, since protocols handled by SourceFactories may not be valid protocols for java.net.URL (resulting in a MalformedURLException). So we need a new interface, semantically equivalent to URLFactory, but returning a String instead of an URL. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
