Difference between revisions of "Xebra Documentation"
(→Error Responses) |
(→Xebra Libraries) |
||
| Line 42: | Line 42: | ||
=== Http === | === Http === | ||
=== Utilities === | === Utilities === | ||
| + | === Thread Utilities === | ||
| + | === AST Elements === | ||
| + | === Taglibrary Base === | ||
| + | === Taglibrary Form === | ||
| + | === Taglibrary XRPC === | ||
| + | === Tags === | ||
Revision as of 11:33, 28 August 2009
About | Installation | Documentation | Tutorials | Frequently Asked Questions
Contents
Overview
Xebra HTTP Server Plugins
Mod_xebra for Apache
Xebra Server
Web Applications
Xebra Tag Libraries
On the following pages you can find the descriptions of the different tags of the available tag libraries.
Master pages
XML_RPC
Code documentation
Xebra Libraries
Error
Provides internal error types for all xebra applications such as XERROR_CANNOT_OPEN_FILE or XERROR_SOCKET_NOT_BOUND. These errors are not supplied to the browser but only displayed in the log/console.
Common
Error Responses
Classes from xebra_error_responses are split into XER_SERVER: error responses generated by the server and XER_APP: error responses generated by the webapp. Both types are ultimately sent to the http server plugin and displayed in the user's browser. For instance XER_POST_TOO_BIG is a server error response that is created if the post request is bigger than allowed. XER_APP_CANNOT_FIND_PAGE is a response created by the webapp and then sent to the server if no servlet with the specified name was defined.
