cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benson Margulies (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CXF-1087) Spring control of jetty server
Date Thu, 15 Oct 2009 00:35:31 GMT

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

Benson Margulies resolved CXF-1087.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2.5
                   2.1.8

I have a rather strong memory that something was done about this.


> Spring control of jetty server
> ------------------------------
>
>                 Key: CXF-1087
>                 URL: https://issues.apache.org/jira/browse/CXF-1087
>             Project: CXF
>          Issue Type: Improvement
>          Components: Bus
>    Affects Versions: 2.0.2
>            Reporter: Benson Margulies
>             Fix For: 2.1.8, 2.2.5
>
>
> The current design of the jetty integration is that the Jetty server is a hidden, static,
shared, resource of the buses. This is fine, until someone wants to create (and perhaps clean
up) a completely self-contained environment. It is a tradeoff: the current design allows an
app to make multiple busses that deploy services on the same HTTP port(s), but it offers no
direct way to control the lifecycle of the server.
> I would propose, as an idea, a property on the http engine bean which controls this.
If set to the non-default value, the engine will be considered a resident of the bus. If it
thus ends up on a fight over a port with some other server associated with some other bus,
so be it. When the bus is shutdown, such a server would go away. Period.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message