juneau-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Blackmon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JUNEAU-62) Support complete customization of jetty runtime
Date Tue, 01 Aug 2017 19:35:00 GMT

    [ https://issues.apache.org/jira/browse/JUNEAU-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16109596#comment-16109596
] 

Steve Blackmon commented on JUNEAU-62:
--------------------------------------

makes sense to me.  there are more complex but common use cases such as run HTTP on one port
and HTTPS on another where it's just easier to configure jetty directly.

> 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
>   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
(v6.4.14#64029)

Mime
View raw message