Apache Cocoon is a web development framework built around the concepts of separation of concerns and component-based web development.
Cocoon implements these concepts around the notion of 'component pipelines', each component on the pipeline specializing on a particular operation. This makes it possible to use a Lego(tm)-like approach in building web solutions, hooking together components into pipelines without any required programming.
Cocoon is "web glue for your web application development needs". It is a glue that keeps concerns separate and allows parallel evolution of all aspects of a web application, improving development pace and reducing the chance of conflicts.
XHTMLSerializer: Don't encode characters in <script> and <style> elements to avoid JavaScript parsing errors. This behaviour has been pulled up from the HTMLSerializer. Fixes https://issues.apache.org/jira/browse/COCOON-2249.
XHTMLSerializer: Don't encode characters in <script> and <style> elements to avoid JavaScript parsing errors. This behaviour has been pulled up from the HTMLSerializer. Fixes https://issues.apache.org/jira/browse/COCOON-2249.
COCOON-2241 - The commandline is not working since COCOON-1985. In COCOON-1985 it was introduced a lock to prevent problems in concurrent situations. This code change was not tested with the CLI mode of cocoon since the cli environment does not store the http-requested object. The introduced solution looks wheter the http-request object is null if so we will test whether we are in cli mode and lock this object instead.
Introduce support servlet: protocol in flow's sendPage function.
The previous behaviour was that if one called sendPage("some/path") it would be translated into redirection to "cocoon:/some/path" so any custom protocol was disallowed in sendPage calls.
Now default behaviour is preserved but additionally one can use servlet: protocol explicitly in sendPage calls.
In order to achieve that some extensions to ForwardRedirector and ConcreteTreeProcessor were introduced for special handling of "servlet:" protocol.
Current implementation does not really redirect in sense of Cocoon's internals but just makes a new request using ServletSource and after processing is finished it just copies the response to current environment.
As consequence of this change, also <map:redirect-to uri="servlet:/some/path"/> is supported.
Introduce support servlet: protocol in flow's sendPage function.
The previous behaviour was that if one called sendPage("some/path") it would be translated into redirection to "cocoon:/some/path" so any custom protocol was disallowed in sendPage calls.
Now default behaviour is preserved but additionally one can use servlet: protocol explicitly in sendPage calls.
In order to achieve that some extensions to ForwardRedirector and ConcreteTreeProcessor were introduced for special handling of "servlet:" protocol.
Current implementation does not really redirect in sense of Cocoon's internals but just makes a new request using ServletSource and after processing is finished it just copies the response to current environment.
As consequence of this change, also <map:redirect-to uri="servlet:/some/path"/> is supported.
