[
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Sasvari updated OOZIE-2666:
----------------------------------
Attachment: OOZIE-2666.PATCH-27.patch
> Support embedding Jetty into Oozie
> ----------------------------------
>
> Key: OOZIE-2666
> URL: https://issues.apache.org/jira/browse/OOZIE-2666
> Project: Oozie
> Issue Type: Sub-task
> Components: core
> Reporter: Attila Sasvari
> Assignee: Attila Sasvari
> Attachments: OOZIE-2666.PATCH-01.patch, OOZIE-2666.PATCH-02.patch,
> OOZIE-2666.PATCH-03.patch, OOZIE-2666.PATCH-05.patch,
> OOZIE-2666.PATCH-06.patch, OOZIE-2666.PATCH-07.patch,
> OOZIE-2666.PATCH-09.patch, OOZIE-2666.PATCH-10.patch,
> OOZIE-2666.PATCH-11.patch, OOZIE-2666.PATCH-12.patch,
> OOZIE-2666.PATCH-13.patch, OOZIE-2666.PATCH-14.patch,
> OOZIE-2666.PATCH-15.patch, OOZIE-2666.PATCH-16.patch,
> OOZIE-2666.PATCH-17.patch, OOZIE-2666.PATCH-18.patch,
> OOZIE-2666.PATCH-19.patch, OOZIE-2666.PATCH-20.patch,
> OOZIE-2666.PATCH-21.patch, OOZIE-2666.PATCH-22.patch,
> OOZIE-2666.PATCH-23.patch, OOZIE-2666.PATCH-24.patch,
> OOZIE-2666.PATCH-25.patch, OOZIE-2666.PATCH-27.patch
>
>
> The purpose of this task is to allow Oozie to run as a standalone application
> rather than being deployed to a container inside a WAR file.
> - Build embedded jetty enabled Oozie by default
> - Allow building Tomcat based Oozie by specifying the 'tomcat' profile
> - Starting Oozie with oozied.sh detect webserver type based on the build info
> - Oozie Web UI is working with JDK 8 if using embedded jetty
> - If using Jetty, allow the user to configure the following settings via
> oozie-default / oozie-site xml:
> -- request / response header size
> -- allowed HTTPS protocols
> -- excluded / weak cipher suites
> -- threadpool size
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
