-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update of README.md for release version 3.0
- Loading branch information
1 parent
75a0a1a
commit caf210e
Showing
1 changed file
with
4 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,15 +1,15 @@ | ||
# XSLWeb | ||
###Web application framework for XSLT developers | ||
XSLWeb is an open source and free to use web development framework for XSLT developers. It is based on concepts similar to frameworks like [Cocoon](http://cocoon.apache.org/) and [Servlex](http://servlex.net/), but aims to be more easily accessible and pragmatic. | ||
### Web application framework for XSLT and XQuery developers | ||
XSLWeb is an open source and free to use web development framework for XSLT and XQuery developers. It is based on concepts similar to frameworks like [Cocoon](http://cocoon.apache.org/) and [Servlex](http://servlex.net/), but aims to be more easily accessible and pragmatic. | ||
|
||
Using XSLWeb, XSLT developers can develop both web applications (dynamic websites) and web services. In essence, an XSLWeb web application is a set of XSLT stylesheets that transform an XML representation of the HTTP request (the *Request XML*) to an XML representation of the HTTP response (the *Response XML*). Which specific XSLT stylesheet or pipeline of XSLT stylesheets must be executed for a particular HTTP request is governed by another XSLT stylesheet, the request dispatcher stylesheet. | ||
Using XSLWeb, XSLT/XQuery developers can develop both web applications (dynamic websites) and web services. In essence, an XSLWeb web application is one or more XSLT stylesheets or XQueries that transform an XML representation of the HTTP request (the *Request XML*) to an XML representation of the HTTP response (the *Response XML*). Which specific (pipeline of) XSLT stylesheet or XQueries must be executed for a particular HTTP request is governed by another XSLT stylesheet, the *Request Dispatcher stylesheet*. | ||
|
||
After every XSLT transformation step, an optional validation pipeline step (XML Schema or Schematron) can be added to validate the result of the previous transformation step. | ||
|
||
During transformations, data sources can be accessed using a built-in library of extension functions that provide HTTP communication (for example to consume REST or SOAP based web services), file and directory access, relational database access and so on. | ||
|
||
The result of a pipeline can be serialized to XML, (X)HTML or plain text and using specific serializer pipeline steps to JSON, ZIP files, PDF, Postscript or RTF (using XSL:FO and Apache FOP). | ||
|
||
See [Quick Start Guide](https://github.com/Armatiek/xslweb/blob/master/docs/XSLWeb_2_0_Quick_Start.pdf). | ||
See [Quick Start Guide](https://github.com/Armatiek/xslweb/blob/master/docs/XSLWeb_3_0_Quick_Start.pdf). | ||
|
||
![XSLWeb HTTP request to response flow](https://raw.githubusercontent.com/Armatiek/xslweb/master/docs/xslweb_flow.png) |