[
https://issues.apache.org/jira/browse/FELIX-5735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16225209#comment-16225209
]
Carsten Ziegeler commented on FELIX-5735:
-----------------------------------------
I agree that with adding support for factory configurations we created
something an interesting configuration setup: you can configure one jetty with
a configuration. If you want to have N instances listening on different ports,
you can either use a normal configuration plus N-1 factory configurations or N
factory configurations and disable the default server. Not nice but the only
way to get this in a compatible way.
As Jan Willem notes, we already have a way to disable the default setup by
specifying 0 as the port. So I think we can close this issue
> No possibility to deactivate the startup of the default server
> --------------------------------------------------------------
>
> Key: FELIX-5735
> URL: https://issues.apache.org/jira/browse/FELIX-5735
> Project: Felix
> Issue Type: Bug
> Components: HTTP Service
> Affects Versions: http.jetty-3.4.4
> Reporter: Jürgen Albert
>
> As far as I have seen, I can change the configuration of the default jetty,
> but there is no way to suppress the start of a server. We have a couple of
> cases, where we only want to start one or more server instances on demand.
> a system variable to prevent the startup could be a solution here.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
