|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | |||||||||
| Interface Summary | |
|---|---|
| ClassLoaderReporter | Allows a bean to report the classloader that is appropriate for it and will be used
for dispatching into this beans environment, this is only needed in advanced
cases and should not normally be implemented The primary use case here is to allow someone to set their classloader when they are using a proxied bean or the implementation class is in the wrong classloader This is primarily used in the case of the HttpServletAccessProvider
or EntityViewAccessProvider
and the implementations of those should also implement this interface
to be able to specify the classloader |
| Class Summary | |
|---|---|
| EntityResponse | This is here to contain the information we get back from an entity (http) request fired
by the EntityBroker.fireEntityRequest(String, String, String, Map, Object) methodThis object and the data in it should be considered immutable |
| SakaiToolData | This contains an abstraction of the information about a tool in Sakai |
| TemplateParseUtil | Utility class to handle the URL template parsing (entity template parsing) |
| TemplateParseUtil.PreProcessedTemplate | Contains the data for templates, each template must have a template key and the template itself |
| TemplateParseUtil.ProcessedTemplate | Contains the processed template with the values from the processed input string that was determined to be related to this template |
| TemplateParseUtil.Template | Represents a parseable template (which is basically a key and the template string),
the array which defines the set of template keys is TemplateParseUtil.PARSE_TEMPLATE_KEYSRules for parse templates: 1) "{","}", and TemplateParseUtil.SEPARATOR are special characters and must be used as indicated only
2) Must begin with a TemplateParseUtil.SEPARATOR, must not end with a TemplateParseUtil.SEPARATOR
3) must begin with "/{prefix}" (use the TemplateParseUtil.SEPARATOR and TemplateParseUtil.PREFIX constants)
3) each {var} can only be used once in a template
4) {var} can never touch each other (i.e /{var1}{var2}/{id} is invalid)
5) each {var} can only have the chars from TemplateParseUtil.VALID_VAR_CHARS
6) parse templates can only have the chars from TemplateParseUtil.VALID_TEMPLATE_CHARS
7) Empty braces ({}) cannot appear in the template |
|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | |||||||||