juneau-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Bognar (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (JUNEAU-62) Support complete customization of jetty runtime
Date Mon, 07 Aug 2017 19:51:00 GMT

     [ https://issues.apache.org/jira/browse/JUNEAU-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

James Bognar resolved JUNEAU-62.
       Resolution: Fixed
         Assignee: James Bognar
    Fix Version/s: 6.3.2

Microservices now specify a barebones jetty.xml in the working folder that can be configured
to do whatever is supported by Jetty.  Authentication/SSL feature support have been removed
from the cfg file and now must be configured in the jetty.xml file.

> Support complete customization of jetty runtime
> -----------------------------------------------
>                 Key: JUNEAU-62
>                 URL: https://issues.apache.org/jira/browse/JUNEAU-62
>             Project: Juneau
>          Issue Type: New Feature
>            Reporter: Steve Blackmon
>            Assignee: James Bognar
>             Fix For: 6.3.2
>   Original Estimate: 1h
>  Remaining Estimate: 1h
> When launching RestMicroservice, there are a finite set of configuration options for
Jetty supported by juneau.
> I think it would make more sense to let a user configure jetty directly, rather than
copying just a handful of popular settings one by one from the juneau config.
> Proposed solution:
> On start-up RestMicroservice looks for a filesystem jetty.xml, falls back to a default
resource managing in rest-microservice/src/main/resources.
> After creating the Server instance, supported properties such as SSL settings get copied
from application.cfg into Server
> Then the server starts up.
> In this way, it won't require any new code to run RestMicroservice using a highly custom
jetty config.

This message was sent by Atlassian JIRA

View raw message