webwork.properties的属性配置
|
webwork.properties的属性配置（转载 ### Webwork default properties###(can be overridden by a webwork.properties file in the root of the classpath)###### Specifies the Configuration used to configure webwork### one could extend com.opensymphony.webwork.config.Configuration### to build one's customize way of getting the configurations parameters into webwork# webwork.configuration=com.opensymphony.webwork.config.DefaultConfiguration### This can be used to set your default locale and encoding scheme# webwork.locale=en_USwebwork.i18n.encoding=UTF-8### if specified, the default object factory can be overridden here### Note: short-hand notation is supported in some cases, such as "spring"### Alternatively, you can provide a com.opensymphony.xwork.ObjectFactory subclass name here # webwork.objectFactory = spring### specifies the autoWiring logic when using the SpringObjectFactory.### valid values are: name, type, auto, and constructor (name is the default)webwork.objectFactory.spring.autoWire=name### indicates to the webwork-spring integration if Class instances should be cached### this should, until a future Spring release makes it possible, be left as true### unless you know exactly what you are doing!### valid values are: true, false (true is the default)webwork.objectFactory.spring.useClassCache=true### if specified, the default object type determiner can be overridden here### Note: short-hand notation is supported in some cases, such as "tiger" or "notiger"### Alternatively, you can provide a com.opensymphony.xwork.util.ObjectTypeDeterminer implementation name here### Note: if you have the xwork-tiger.jar within your classpath, GenericsObjectTypeDeterminer is used by default### To disable tiger support use the "notiger" property value here.#webwork.objectTypeDeterminer=tiger#webwork.objectTypeDeterminer=notiger### Parser to handle HTTP POST requests, encoded using the MIME-type multipart/form-data# webwork.multipart.parser=cos# webwork.multipart.parser=pellwebwork.multipart.parser=jakarta# uses javax.servlet.context.tempdir by defaultwebwork.multipart.saveDir=webwork.multipart.maxSize=2097152### Load custom property files (does not override webwork.properties!)# webwork.custom.properties=application,com/webwork/extension/custom### How request URLs are mapped to and from actionswebwork.mapper.class=com.opensymphony.webwork.dispatcher.mapper.DefaultActionMapper### Used by the DefaultActionMapper### You may provide a comma separated list, e.g. webwork.action.extension=action,jnlp,dowebwork.action.extension=action### CompositeActionMapper# if we use a CompositeActionMapper, we could define the the ActionMappers# that will be consulted as follows. ActionMapper with lower order takes# precedence :-#webwork.mapper.class=com.opensymphony.webwork.dispatcher.mapper.CompositeActionMapper#webwork.compositeActionMapper.1=com.opensymphony.webwork.dispatcher.mapper.RestfulActionMapper#webwork.compositeActionMapper.2=com.opensymphony.webwork.dispatcher.mapper.DefaultActionMapper### Used by FilterDispatcher### If true than WW serves static content from inside its jar. ### If false than the static content must be available at <context_path>/webworkwebwork.serve.static=true### use alternative syntax that requires %{} in most places### to evaluate expressions for String attributes for tagswebwork.tag.altSyntax=true### when set to true, WebWork will act much more friendly for developers. This### includes:### - webwork.i18n.reload = true### - webwork.configuration.xml.reload = true### - raising various debug or ignorable problems to errors### For example: normally a request to foo.action?someUnknownField=true should### be ignored (given that any value can come from the web and it### should not be trusted). However, during development, it may be### useful to know when these errors are happening and be told of### them right away.webwork.devMode=false### when set to true, resource bundles will be reloaded on _every_ request.### this is good during development, but should never be used in productionwebwork.i18n.reload=false### Standard UI theme### Change this to reflect which path should be used for JSP control tag templates by defaultwebwork.ui.theme=xhtmlwebwork.ui.templateDir=template#sets the default template type. Either ftl, vm, or jspwebwork.ui.templateSuffix=ftl### Configuration reloading### This will cause the configuration to reload xwork.xml when it is changedwebwork.configuration.xml.reload=false### Location of velocity.properties file. defaults to velocity.properties# webwork.velocity.configfile=velocity.properties### Comma separated list of VelocityContext classnames to chain to the WebWorkVelocityContext# webwork.velocity.contexts=### used to build URLs, such as the UrlTagwebwork.url.http.port=80webwork.url.https.port=443### possible values are: none, get or allwebwork.url.includeParams=get### Load custom default resource bundles# webwork.custom.i18n.resources=testmessages,testmessages2### workaround for some app servers that don't handle HttpServletRequest.getParameterMap()### often used for WebLogic, Orion, and OC4Jwebwork.dispatcher.parametersWorkaround=false### configure the Freemarker Manager class to be used### Allows user to plug-in customised Freemarker Manager if necessary### MUST extends off com.opensymphony.webwork.views.freemarker.FreemarkerManager#webwork.freemarker.manager.classname=com.opensymphony.webwork.views.freemarker.FreemarkerManager### See the WebWorkBeanWrapper javadocs for more informationwebwork.freemarker.wrapper.altMap=true### configure the XSLTResult class to use stylesheet caching.### Set to true for developers and false for production.webwork.xslt.nocache=false### insert Freemarker's Sitemesh applydecorator transform to be put### into freemarker's model allowing sitemesh's applydecorator tag to ### be used in freemarker's page eg.### <@sitemesh.applydecorator name="someDecorator" page="/pages/somePage.ftl" />#webwork.freemarker.sitemesh.applyDecoratorTransform=true### A start up listener class name (must implements com.opensymphony.webwork.dispatcher.StartUpListener ### interface) that will get invoked only once when WebWork started up. The class names could be ### comma separated and will be executed in order.##webwork.dispatcher.startUpListener=foo.bar.StartUpListener1,foo.bar.StartUpListener2### A shut down listener class name (must implements com.opensymphony.webwork.dispatcher.ShutDownListener### interface) that will get invoked only once when WebWork shuts down. The class names could be### comma separated and will be executed in order.##webwork.dispatcher.shutDownListener=foo.bar.ShutDownListener1,foo.bar.ShutDownListener2 default.properties是Webwork的缺省配置文件,可以被classpath根目录下的 webwork.properties 文件覆盖 配置工厂 指定用来配置webwork的 Configuration. 指定locale,编码 用来设置你的缺省 locale和编码方案 Object Factory 如果指定了,缺省的ojbect factory在这里可以被覆盖 自动装配策略 指定当使用SpringObjectFactory时的自动装配逻辑. 类缓存 标识webwork-spring集成,如果类实例应该被缓存 缺省对象类型裁决者 如果设定了,缺省的对象类型裁决者可以被覆盖 注意: 缩写在某些情况下支持,例如 "tiger" or "notiger" 文件上传设置 用来处理HTTP POST请求,编码使用MIME-type multipart/form-data方式的 定制配置 装载定制的属性文件(不会覆盖webwork.properties!) 缺省URL映射处理器 用来处理request URL如何映射到action,或者相反的映射(用户可以实现自己的处理) 缺省后缀 DefaultActionMapper使用的设置 是否静态文件由FilterDispatcher服务 FilterDispatcher使用的设置 标签语法设定 使用 alternative syntax 在大多数地方需要 %{} 来计算标签的字符串属性的值 开发模式设定 当设置为true时,WebWork会对开发者更友好.这包括: 国际化资源设定 当设置为true,资源包会在每个请求时自动重新载入. theme和模板设定 标准的UI theme 设置缺省模板类型,可以是ftl,vm,jsp 配置自动更新设定 配置自动重新装载,这会导致配置来重新载入xwork.xml, 当它改变的时候 Velocity配置设定 velocity.properties 文件的位置.缺省是 velocity.properties 逗号分割的 VelocityContext 类名来链接到 WebWorkVelocityContext URL相关设定 用来构建URL,例如UrlTag 自定义国际化资源 装载自定义的缺省资源包(如果有多个,用逗号分割) 应用服务器相关设定 有些app server不能处理HttpServletRequest.getParameterMap(),经常使用的是WebLogic,Orion和OC4J FreeMarker相关设定 配置要用的 Freemarker Manager 类 允许用户插入自定义的 Freemarker Manager ,如果需要的话 浏览 WebWorkBeanWrapper 的javadoc 了解更多信息 XSLTResult相关设定 配置 XSLTResult 类使用 stylesheet 缓存. |