Well, you always have the option of installing an EntityResolver and then cleanly interface your own code for resolving URLs with XmlBeans.
I can't say I am familiar with URL authentication, but if you think this is something likely to be useful in a variety of cases, and that can be implemented in a generic way, then you can open a JIRA enhancement request (http://issues.apache.org/jira/browse/XMLBEANS) and we'll take it from there. Thanks, Radu -----Original Message----- From: Lendle [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 14, 2005 9:01 PM To: [email protected] Subject: Authentication issues not handled For example, when using scomp to get schemas from a URL, it is possible that the URL is password protected via BASIC or DIGEST http authentication method. It seems like the xmlbean does not handle this. We know that in simple case we can just use Authenticator.setDefault(...) to overcome the problem, however, if the URL requires authentication over SSL, there seems no good way to handle except modify xmlbeans' source code. Moreover, if the given URL uses protocols like SMB to access windows network neighborhood, it just much harder to deal with it without modifying the xmlbeans' source code. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
