web server - Borland Technical Publications
web server - Borland Technical Publications web server - Borland Technical Publications
Chapter 10 10Web applications bundled with BES Chapter About Cocoon This section describes the Apache Cocoon and Apache Struts for which BES includes support. For more information about Apache, go the 3rd Party Documentation. The Cocoon servlet is pre-installed in the Tomcat web container upon which the Borland web container is based. The Struts framework is also pre-installed in the Borland web container. For more information about the Borland web container, go to Chapter 4, “Web components.” Cocoon is a web publishing framework that renders XML data into a number of formats including HTML, WML, PDF, and the like. These formats are based on a set of properties provided by an XSL stylesheet. All BES product offerings include the Cocoon servlet pre-installed in the Borland web container. The web.xml file contains specifications for the Cocoon servlet, which is preconfigured to point to the cocoon properties file in the WEB-INF directory of the context under which Cocoon is invoked. However, you can change this specification to point to another location. Additionally, the web.xml file includes a mapping for “*.xml” directing any such file to be processed by Cocoon. This mapping can be modified or deleted. An unmodified copy of the properties file is included as part of the Cocoon webapp (cocoon.war) distributed with BES. You can customize this file to create your own cocoon.properties file. This unmodified cocoon.properties file is compiled in with the Borland web container. As the default properties file, it is used whenever the file specified in the Cocoon servlet definition cannot be found. Cocoon is an open-source product distributed by the Apache Software Foundation. For additional information about Cocoon, see the web site: http://xml.apache.org/cocoon/ Chapter 10: Web applications bundled with BES 83
84 BES Developer’s Guide
- Page 43 and 44: Borland web container implementatio
- Page 45 and 46: Borland web container implementatio
- Page 47 and 48: Borland web container implementatio
- Page 49 and 50: Smart Agent implementation Smart Ag
- Page 51 and 52: 40 BES Developer’s Guide
- Page 53 and 54: Apache web server to Borland web co
- Page 55 and 56: Apache web server to Borland web co
- Page 57 and 58: Apache web server to Borland web co
- Page 59 and 60: Large data transfer Downloading lar
- Page 61 and 62: Large data transfer Uploading large
- Page 63 and 64: IIS web server to Borland web conta
- Page 65 and 66: IIS web server to Borland web conta
- Page 67 and 68: IIS web server to Borland web conta
- Page 69 and 70: Session management with JSS If an i
- Page 71 and 72: Managing and configuring the JSS Co
- Page 73 and 74: The Borland IIOP connector BES supp
- Page 75 and 76: Setting up your web container with
- Page 77 and 78: 66 BES Developer’s Guide
- Page 79 and 80: Web-enabling your CORBA server Impo
- Page 81 and 82: Configuring your Apache web server
- Page 83 and 84: Configuring your Apache web server
- Page 85 and 86: Web Services and Partitions ■ ■
- Page 87 and 88: Web Service providers Java:RPC prov
- Page 89 and 90: How Borland Web Services work
- Page 91 and 92: Packaging Web Service Application A
- Page 93: Tools Overview Java2WSDL tool Note
- Page 97 and 98: Client view of an enterprise bean L
- Page 99 and 100: Client view of an enterprise bean E
- Page 101 and 102: Managing transactions Managing tran
- Page 103 and 104: Support for JNDI Support for JNDI T
- Page 105 and 106: EJB to CORBA mapping A CORBA progra
- Page 107 and 108: 96 BES Developer’s Guide
- Page 109 and 110: Application Client architecture Pac
- Page 111 and 112: Document Type Definitions (DTDs) my
- Page 113 and 114: Support of references and links The
- Page 115 and 116: Use of Manifest files Use of Manife
- Page 117 and 118: 106 BES Developer’s Guide
- Page 119 and 120: Sessions in secondary storage If yo
- Page 121 and 122: 110 BES Developer’s Guide
- Page 123 and 124: Container-managed persistence and R
- Page 125 and 126: Implementing an entity bean Generat
- Page 127 and 128: Container-Managed Persistence in Bo
- Page 129 and 130: Container-Managed Persistence in Bo
- Page 131 and 132: Setting Properties Setting Properti
- Page 133 and 134: Setting Properties into a BLOB. The
- Page 135 and 136: Setting Properties Automatic table
- Page 137 and 138: 126 BES Developer’s Guide
- Page 139 and 140: Container-managed persistence and R
- Page 141 and 142: Container-Managed Persistence in Bo
- Page 143 and 144: Container-Managed Persistence in Bo
Chapter<br />
10<br />
10Web applications bundled with BES<br />
Chapter<br />
About Cocoon<br />
This section describes the Apache Cocoon and Apache Struts for which BES includes<br />
support. For more information about Apache, go the 3rd Party Documentation.<br />
The Cocoon servlet is pre-installed in the Tomcat <strong>web</strong> container upon which the<br />
<strong>Borland</strong> <strong>web</strong> container is based. The Struts framework is also pre-installed in the<br />
<strong>Borland</strong> <strong>web</strong> container.<br />
For more information about the <strong>Borland</strong> <strong>web</strong> container, go to Chapter 4, “Web<br />
components.”<br />
Cocoon is a <strong>web</strong> publishing framework that renders XML data into a number of formats<br />
including HTML, WML, PDF, and the like. These formats are based on a set of<br />
properties provided by an XSL stylesheet.<br />
All BES product offerings include the Cocoon servlet pre-installed in the <strong>Borland</strong> <strong>web</strong><br />
container. The <strong>web</strong>.xml file contains specifications for the Cocoon servlet, which is preconfigured<br />
to point to the cocoon properties file in the WEB-INF directory of the context<br />
under which Cocoon is invoked. However, you can change this specification to point to<br />
another location. Additionally, the <strong>web</strong>.xml file includes a mapping for “*.xml” directing<br />
any such file to be processed by Cocoon. This mapping can be modified or deleted.<br />
An unmodified copy of the properties file is included as part of the Cocoon <strong>web</strong>app<br />
(cocoon.war) distributed with BES. You can customize this file to create your own<br />
cocoon.properties file. This unmodified cocoon.properties file is compiled in with the<br />
<strong>Borland</strong> <strong>web</strong> container. As the default properties file, it is used whenever the file<br />
specified in the Cocoon servlet definition cannot be found.<br />
Cocoon is an open-source product distributed by the Apache Software Foundation. For<br />
additional information about Cocoon, see the <strong>web</strong> site: http://xml.apache.org/cocoon/<br />
Chapter 10: Web applications bundled with BES 83