| tc-config.xml (Client) | |
| 001: | <?xml version="1.0" encoding="UTF-8"?> |
| 002: | <!-- |
| 003: | |
| 004: | All content copyright (c) 2003-2008 Terracotta, Inc., |
| 005: | except as may otherwise be noted in a separate copyright notice. |
| 006: | All rights reserved. |
| 007: | |
| 008: | --> |
| 009: | <tc:tc-config xmlns:tc="http://www.terracotta.org/config" |
| 010: | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" |
| 011: | xsi:schemaLocation="http://www.terracotta.org/schema/terracotta-4.xsd"> |
| 012: | <!-- Server is colocated with client and DSO is listening on |
| 013: | default port (9510). --> |
| 014: | <servers> |
| 015: | <server host="%i" name="sample"/> |
| 016: | <update-check> |
| 017: | <enabled>true</enabled> |
| 018: | </update-check> |
| 019: | </servers> |
| 020: | |
| 021: | <!-- Tell DSO where to put the generated client logs |
| 022: | See the Terracotta Configuration Guide and Reference for additional |
| 023: | information. --> |
| 024: | <clients> |
| 025: | <logs>terracotta/client-logs/spring/webflow/%D</logs> |
| 026: | <statistics>terracotta/client-statistics/spring/webflow/%D</statistics> |
| 027: | </clients> |
| 028: | |
| 029: | <application> |
| 030: | <!-- See the Terracotta Spring Guide for more details of the the <spring/> |
| 031: | section of the tc-config file --> |
| 032: | <spring> |
| 033: | <!-- Tell DSO about the webapp we're sharing --> |
| 034: | <jee-application name="*webflow*"> |
| 035: | <!-- Enable sessions --> |
| 036: | <session-support>true</session-support> |
| 037: | <!-- Our app requires these custom objects/classes to be shared - the following declarations |
| 038: | tells DSO which ones they are. When the app runs under DSO, instances of these classes |
| 039: | will broadcast changes in their state. |
| 040: | |
| 041: | A good idiom when writing an app that you intend to cluster via TC DSO, is to group the |
| 042: | classes you wish to share under a single package (although if you follow the MVC pattern |
| 043: | this tends to happen naturally) - this way the list of classes you wish to instrument |
| 044: | can be concise --> |
| 045: | <instrumented-classes> |
| 046: | <include> |
| 047: | <!-- Here, we say, instrument the 'demo.webflow.WebFlowBean' bean class --> |
| 048: | <class-expression>demo.webflow.WebFlowBean</class-expression> |
| 049: | </include> |
| 050: | </instrumented-classes> |
| 051: | </jee-application> |
| 052: | </spring> |
| 053: | </application> |
| 054: | </tc:tc-config> |