Carsten Ziegeler [[EMAIL PROTECTED]] wrote: > As far as I know, the store and the sourceresolver packages have never > been released until now. We *could* release store, but we can't release > the sourceresolver package as some changes still have to be made, so you > can consider it ALPHA stage.
3 month ago I raised an issue on this list, concerning the following method call in SourceResolverImpl.contextualize ( (File)m_context.get( "context-root" ) ).toURL() The toURL method accesses System-variables (and the local file-system) when trying to convert the file to an URL, and raises a SecurityException, if called in an sandboxed environment (e.g. webstart). The SourceResolverImpl class is needed internally by the ContextManger to resolve the locations of the configuration-files. But with applets or webstart clients these configurations are normally located on the server and "context-root" should be something like "http://myserver.mydomain:myport/mycontext"; instead of a File-Object. To workaround this problem I pass the already resolved Configurations to the Fortress ContextManager, instead of using the SourceResolver. But that doesn't prevent the SecurityException, because the contextualize method of SourceResolverImpl is called even if there is nothing to resolve. Leo Suic proposed the following change to the contextualize method: if( m_context.get( "context-root" ) instanceof URL ) { m_baseURL = (URL)m_context.get( "context-root" ); } else { m_baseURL = ( (File)m_context.get( "context-root" ) ).toURL(); } which would allow the context-root entry to be a URL as well. The change would be backwards compatible. There were no replies to this proposal, so I presume it got lost in the traffic. Regards Christopher -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
