Community
Participate
Working Groups
The URI will be used in SysLib.getResource and @Resource. The existing single segment name must continue to work. The URI could include a context, name, and type. Currently the only type is binding. The context for binding is the properties file that would contain the binding.
Created attachment 209968 [details] Resource URI proposal The attached document is the proposed format for resource URI's.
Created attachment 210125 [details] Specification for Resource URIs The URI format will be URI = resource:sub-scheme ":" hier-part [ "?" query ] [ "#" fragment ] The resource scheme is optional, sub-scheme's are required. The current @Resource and getResource used to get bindings will change from using a simple name to a URI. The URI definition is: -binding:<resource binding name> this assumes the default egldd file as the source of the resource binding information. -binding:file:/<property file name>#<resource binding name> specifies the property file name as the source of the resource binding information. This affects all @Resource annotations and all SysLib.getResource function invocations. See the attached for details.
specification updated for 0.8.0 content.
Created attachment 210226 [details] Specification for Resource URIs show file uri's as relative paths not absolute
completed
