📄 resin-3.0.1.xtp
字号:
<document> <header> <product>resin</product> <title>Resin 3.0.1 Beta Release Notes</title> </header><body><summary objsummary="localtoc"/><s1 title="Overview"><p>Resin 3.0.1 is the second beta release of Resin 3.0.x.</p><p>Because of the large number of changes, developers should stresstest their application with Resin 3.0.1 thoroughly before deployingit.</p><p>We are calling the Resin 3.0.x series "beta". The "production"versions will be the Resin 3.1.x series. The two reasons for callingthe code "beta" is the large number of changes, and because we areexpecting to add a great deal of features to following 3.0.xreleases. For many users, the stability of 3.0.x will be sufficientfor deployment, but we wanted to give an extra warning to make surethat people stress tested their applications before deploying on 3.0.x.</p></s1><s1 title="JSP 2.0 and Servlet 2.4 drafts"><p>Resin 3.0.1 implements the complete JSP 2.0 third draft. Anydiscrepancies should be reported as bugs.</p><p>In particular, Resin 3.0.1 adds support for *.tag and *.tagx files.</p><p>Resin 3.0.1 does not yet include the full support for the thirddraft of Servlet 2.4. In particular, the ERROR dispatch configurationfor filters and the Request listeners have not yet been implemented.</p></s1><s1 title="Persistent Session changes"><p>Resin 3.0.1 includes a large number of persistent sessionchanges. Large parts of that section of Resin has been reimplemented.</p><p>Configuration-wise, the changes should be minimal. The<persistent-store> is configured outside the <session-config>, orfor TCP (cluster) sessions, the <cluster-store> is configured insidethe <cluster> definition itself. Old-style resin.conf and web.xml arestill accepted.</p><s2 title="Passivation changes (change in session-max)"><p>Resin 3.0.1 now allows for many moresessions on disk than in memory. session-max continues to specify themaximum number of sessions allows in memory, but the number of sessionstored on disk may be much larger.</p><p>This change will allow sites to set very large session-timeout values, e.g.24 hours or even 1 month, and allow the sessions to be savedin the persistent store without overloading the memory.</p></s2><s2 title="session owning servers (always-load-session)"><p>jdbc-store now understands the owning server for a session,as tcp-store always has. Now, when a request goes to the owning serverfor the session, the jdbc-store does not need to query the databasefor any updates (backup servers will always need to query the database.</p><p>By saving that query, jdbc-store should now be about as efficient fora load-balanced configuration as tcp-store, as long as theload balancer understands sticky sessions. (If the load balancer alwayssends requests to random servers, there is a smaller probability thatthe request will reach the owning server.)</p></s2><s2 title="CRC checking (always-save-session)"><p>always-save-session now checks the CRC-64 hash of the serializedsession to see if any changes have occurred. If the hash is identical,Resin will know not to save the serialized value, saving either adatabase trip for jdbc-store or a TCP update for cluster-store.The session will still incur the cost of serialization.</p></s2></s1><s1 title="Resources"><p><resource> now recognizes <code>ResourceAdapter</code> and<code>ManagedConnectionFactory</code> resources. If the configuredresource implements <code>ResourceAdapter</code> or<code>ManagedConnectionFactory</code>, Resin will call them with theappropriate lifecycle methods.</p><p>The <a href="examples|jca-connection/index.xtp">Resourcetutorials</a> show how resources can take advantageof these callbacks.</p><s2 title="CronResource (run-at)"><p>The new <a href="examples|jca-cron/index.xtp">CronResource</a> nowreplaces the old run-at servlets. The CronResource accepts anapplication WorkTask which it executes at specific times, configuredfollowing the Unix cron syntax.</p><example title="Cron sample config"><resource type="com.caucho.resources.CronResource"> <init> <cron>10 3,18</cron> <work bean-class="example.WorkTask"> <value>Example</value> <jndi>java:comp/env/example</jndi> </work> </init></resource></example></s2></s1><s1 title="XDoclet"><p>Resin 3.0 now has a limited direct support for EJB/XDoclet generation.The internal XDoclet generator is run as part of <make-loader>, themake classloader. Most of the CMP examples have been expanded touse XDoclet.</p><example title="web.xml"><web-app xmlns="http://caucho.com/ns/resin"> <class-loader> <make-loader path="WEB-INF/classes"> <ejb-doclet srcdir="WEB-INF/classes"/> </make-loader> <compiling-loader path="WEB-INF/classes"/> </class-loader></web-app></example></s1><s1 title="Configuration Changes"> <s2 title="cluster (srun)"><p>The clustering configuration (srun) has changed slightly. The <srun>elements must now be in a <cluster> block.</p><example title="cluster"><resin xmlns="http://caucho.com/ns/resin"> <server> <cluster> <port id='' host='127.0.0.1' port='6802'/> </cluster> ... </server></resin></example><def title="cluster Relax-NG Schema">r_cluster = element cluster { attribute id { string }? & (r_cluster-port* | r_cluster-group*) & r_cluster-store?)}r_cluster-group = element group { r_cluster-port*}r_cluster-port = element port { r_cluster-port-Contents }</def> </s2> <s2 title="persistent store"><p>Persistent store is now configured separately fromthe <session-config>. This will allow the persistent store tomanage distributed objects for things other than sessions and is alsoneeded for the lazy-init to work with cluster store.</p><example title="cluster (TCP) store"><resin xmlns="http://caucho.com/ns/resin"><server> <cluster> <port server-id="a" port='6810' index='1'/> <port server-id="b" port='6811' index='2'/> <cluster-store name="caucho/store" path="session"/> </cluster> <host id=''> <web-app id='/'> <session-config persistent-store="caucho/store"/> </web-app> </host></server></resin></example><example title="JDBC store"><web-app xmlns="http://caucho.com/ns/resin"> <persistent-store name="caucho/store" type="jdbc"> <init> <data-source>jdbc/session</data-source> </init> </persistent-store> <session-config persistent-store="caucho/store"/></web-app></example><def title="persistent-store Relax-NG Schema">r_persistent-store = element persistent-store { r_name, (attribute type { string } | element type { string }), init?}r_cluster-store = element cluster-store { (attribute name { string } | element name { string })?, (attribute path { string } | element path { string }), (attribute always-load { string } | element always-load { string })?, (attribute always-save { string } | element always-save { string })?}</def> </s2> <s2 title="dependency"><p>Resin 3.0.1 adds experimental support for custom dependency checking.With <dependency>, a web.xml can specify that the Application shouldbe restarted when a specified file changes,just like the web.xml. For example, a user could specifythe struts-config.xml.</p><example title="dependency"><web-app xmlns="http://caucho.com/ns/resin"> <dependency path="WEB-INF/struts-config.xml"/> ...</web-app></example><def title="dependency Relax-NG Schema">r_dependency = element dependency { (attribute path { string } | element path { string })}</def> </s2> <s2 title="ear-deploy"><p>Resin 3.0.1 adds preliminary support for EAR files withthe <ear-deploy> configuration element. The deployment directory,specified by the <var>path</var>, is the location for the .ear file. Thatdirectly may safely coexist with the <var>webapps</var> directory, since theexpanded directory names are unique.</p><p><ear-deploy> may occur in the <host> andthe <web-app> context.</p><def title="ear-deploy Relax-NG Schema">r_ear-deploy = element ear-deploy { (attribute url-prefix { string } | element url-prefix { string })? & (attribute path { r_path } | element path { r_path }) & (attribute expand-path { r_path } | element expand-path { r_path })? & r_lazy-init?}</def> </s2> <s2 title="resource-deploy"><p>Resin 3.0.1 adds preliminary support for RAR files withthe <resource-deploy> configuration element. The deployment directory,specified by the <var>path</var>, is the location for the .rar file. Thatdirectly may safely coexist with the <var>webapps</var> directory, since theexpanded directory names are unique.</p><p><resource-deploy> may occur in any environment context, e.g. <server>,<host>, or <web-app>.</p><p>The resources found by the<resource-deploy> are configured and created with the<connector> element.</p><def title="resource-deploy Relax-NG Schema">r_resource-deploy = element resource-deploy { (attribute path { string } | element path { string }) & (attribute expand-path { string } | element expand-path { string })?}</def> </s2> <s2 title="connector"><p>The new connector element is used to configure .rar resources.Old style connectors will have a single <connection-factory> interface.New-style connectors (Connector 1.5) can include a separate<resource-adapter> configuration.</p><example title="web.xml with connector config"><web-app xmlns="http://caucho.com/ns/resin"> <resource-deploy path="WEB-INF/deploy"/> <connector type="example.TestResourceFactory"> <connection-factory name="jca/t1"> <init><value>a</value></init> </connection-factory> </connector></web-app></example><def title="connector Relax-NG Schema">r_connector = element connector { r_type & r_resource-adapter? & r_connection-factory*}r_connection-factory = element connection-factory { r_name, r_type?, r_init?}r_resource-adapter = element resource-adapter { r_name?, r_init?}</def> </s2></s1><s1 title="Limitations"><ol><li>libresin.so will not yet compile for MacOS-X. Resin will still run without it, but OpenSSL is not available and the JNI enhancements are not available either.</li><li>The IIS and Apache plugins are still definitely of experimental quality.</li></ol></s1></body></document>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -