📄 resin-3.0.4.xtp
字号:
<document> <header> <product>resin</product> <title>Resin 3.0.4 Release Notes</title> </header><body><summary objsummary="localtoc"/><s1 title="Overview"><p>Any bug you find in 3.0.4 should be reported in the<a href="http://www.caucho.com/quercus/bugtrack">bugtrack</a>.</p><p>Because of the large number of changes from Resin 2.1 to Resin 3.0,developers should stresstest their application with Resin 3.0.4 thoroughly before deployingit.</p></s1><s1 title="Thread Pooling"><p>The thread pooling and connection management has changeddramatically for Resin 3.0.4. With the exception of the new<thread-pool> configuration, this should be invisible for mostusers except as a gain in scalability.</p><p>Performance for static files is now essentially the same asApache 2.</p><p>The new thread model now better supports large number ofsimultaneous connections, e.g. 300 and 500 simultaneousopen sockets.</p><p>The single thread pool is shared across all of Resin, so theconfiguration is in <resin> and outside of <server>.</p><example><resin xmlns="http://caucho.com/ns/resin"> <thread-pool> <!-- Maximum number of threads. --> <thread-max>200</thread-max> <!-- Minimum number of spare threads. --> <spare-thread-min>25</spare-thread-min> </thread-pool> <server> ... </server></resin></example><p>The old <connection-pool> has been deprecated and will be removedin Resin 3.0.5.</p></s1><s1 title="Amber"><p><a href="../doc/amber.xtp">Amber</a> is Resin's new persistence manager,currently in development. We have added some <a href="../tutorial/amber-basic/">sample tutorials</a> as a preview. Since the tutorials are directtranslations of the old CMP tutorials, you can compare the twopersistence methods directly.</p><p>We are very excited about the Amber direction and believe it willavoid the complexity of J2EE/EJB for 80% of projects, reducingdevelopment time and engineering cost.</p><p>Amber will likely eventually provide facadesfor Hibernate and JDO 2.0 when that is available. During development,we'll only be supporting Amber's native API.</p><p>Amber currently uses <a href="http://www.hibernate.org">Hibernate's</a> configuration filesand its API model resembles Hibernate, but uses JDBC more directly.Amber's <a href="doc|amber-lifecycle.xtp">lifecycle</a> is patterned afterJDO, using bytecode enhancement to make the JDO state changes possible.</p><p>Amber's JDBC use appears in its queries. Here's an example:</p><example>AmberConnection aConn = ...;ResultSet rs = aConn.query("SELECT course FROM example.Course course");while (rs.next()) { course = (Course) rs.getObject(1); out.println(course.getName() + " is taught by " + course.getTeacher() + "<br>");}</example><example title="directly using query results">AmberConnection aConn = ...;ResultSet rs = aConn.query("SELECT course.name, course.teacher" + " FROM example.Course course" + " ORDER BY course.name");while (rs.next()) { out.println(rs.getString(1) + " is taught by " + rs.getString(2) + "<br>");}</example></s1><s1 title="Persistent Sessions"><p>Persistent session support for JDBC has been enhanced to takeadvantage of clustering and sticky sessions. Each session now has apreferred owning server which reduces the overhead of the sessionpersistence, and removes the need for always-load-session.</p><p>Because of these enhancements, we now recomment jdbc-storeover tcp-store for most configurations.</p><p>The changes affect the configuration files. Because the jdbc storeis now cluster-aware, it needs to be configured in the <cluster>and merely enabled in the <session-config>. A typicalconfiguration will look like the following:</p><example><resin xmlns="http://caucho.com/ns/resin"> <server> <cluster> <srun id="a" port='6810' index='1'/> <srun id="b" port='6811' index='2'/> <cluster-store type="jdbc"> <init> <data-source>jdbc/session</data-source> </init> </cluster-store> </cluster> <web-app-default> <session-config> <cluster-store/> </session-config> </web-app-default> ... </server></resin></example></s1><s1 title="Virtual Host deployment"><p>Virtual hosts can now be deployed like .war files. Virtual hostsdo need to a .jar extension. The <host-deploy> configures thevirtual host deployment.</p><p>Because there is no standard for virtual host deployment, Resinallows the flexibility to configure the layout as the site needs. Werecommend using a pattern following Resin's virtual hosts, the hostroot-directory contains doc/, webapps/ and log/.</p><example><server> <host-deploy path="host-deploy"> <host-default> <document-directory>doc</document-directory> <web-app-deploy path="webapps"/> </host-default> </host-deploy></server></example></s1><s1 title="Servlet 2.4 and JSP 2.0"><p>Because both Servlet 2.4 and JSP 2.0 are still in draft stage,Resin's support is considered beta. However, we don't expectthe specs are likely to change much from the current draft to thefinal draft.</p></s1><s1 title="Smaller Changes"><s2 title="Internationalized Domain Names"><p>Resin now supports RFC3490 for internationalized domain names,the standard for encoding of virtual hosts in non-ascii character sets.The support should be transparent to users.</p></s2><s2 title="log handlers"><p>java.util.logging configuration can now add custom handlers.</p><example><log name="qa.test"> <handler resin:type="qa.MyHandler(file:/tmp/caucho/qa/t${1+2}.log)"/></log></example></s2><s2 title="syslog handler"><p>Resin now supports a custom syslog handler for Unix. Log messageswill be sent by the C syslog() call.</p><example><log name="test.foo" level="warning"> <handler resin:type="com.caucho.log.SyslogHandler"> <facility>daemon<facility> <severity>warning<severity> </handler></log></example></s2><s2 title="web-app-deploy contains web-app-default"><p>The <web-app-deploy> configuration can now include a<web-app-default> that is only applied to the expanded .war files.Applications can use the <web-app-default> and the \${app.name} toadd new configuration files.</p><p>The following allows a WEB-INF/foo.xml configuration fileto configure a foo.war.</p><example><web-app-deploy path="webapps"> <web-app-default> <config-file>WEB-INF/\${app.name}.xml</config-file> </web-app-default></web-app-deploy></example></s2><s2 title="PreparedStatement caching"><p>Resin's database pool can now support PreparedStatementcaching.</p><example><database> <jndi-name>test</jndi-name> <driver type="test.jdbc.TestDriver"> <url>jdbc:test:foo</url> </driver> <prepared-statement-cache-size>8</prepared-statement-cache-size></database></example></s2><s2 title="web-app shutdown changes"><p>Webapps now wait for active request to complete before closing.The time to wait is controlled by shutdown-wait-max.</p><example><web-app-default> <shutdown-wait-max>10s</shutdown-wait-max></web-app-default></example></s2><s2 title="JNI enhancements"><p>Resin has increased its use of JNI for performance. These changeswill be invisible for most users, but if there are bugs, theymay produce some surprising effects whenusing getResource() and getResourceAsStream().</p></s2><s2 title="JavaMail configuration"><p>JavaMail is now configurable with <resource>.</p><example><resource jndi-name='mail/foo' type='javax.mail.Session'> <init mail.host='localhost'/></resource></example></s2><s2 title="Licensing"><p>Resin now displays the current license on startup. Customers whohave purchased license should contact sales@caucho.com for theirlicense files.</p></s2></s1></body></document>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -