Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
MIME-Version: 1.0
Sender: jasonmpell@gmail.com
In-Reply-To: 
 <CACBZuv4m_Y0KzCFe8F+GVZeTgqBxwteFi8NAUtVEhfM-eSatEQ@mail.gmail.com>
References: 
 <CACBZuv5HDnZ3HYfdCTb2_jJnkioMYQ_cXFUft9G7GqvKb7Ay7w@mail.gmail.com>
	<CACBZuv4m_Y0KzCFe8F+GVZeTgqBxwteFi8NAUtVEhfM-eSatEQ@mail.gmail.com>
Date: Thu, 18 Jun 2015 10:38:38 +1000
Message-ID: 
 <CACBZuv5SOB0at0U-cCOasekBnPLAZpUvVRhxXH2AiUkMcVBm=w@mail.gmail.com>
Subject: Re: Enhance ServerLifeCycleListener to include create server event
From: Jason Pell <jason@pellcorp.com>
To: dev@cxf.apache.org
Content-Type: multipart/alternative; boundary=001a1133f1c447234b0518c00778

--001a1133f1c447234b0518c00778
Content-Type: text/plain; charset=UTF-8

Ok I feel stupid.

seems another developer on my team added another spring context loader
which generated the premature event

Please ignore my last 2 emails :-(
On 18/06/2015 10:29 AM, "Jason Pell" <jason@pellcorp.com> wrote:

> after further interrogation of the code the start should have been called
> before spring finished loading
>
> My issue is the ServerRegistry does not contain all the jaxws:endpoints
> when the spring application listener fires.
>
> Anyone got any thoughts as to why?
> On 18/06/2015 9:30 AM, "Jason Pell" <jason@pellcorp.com> wrote:
>
>> Hi,
>>
>> As part of starting up my application I want to know when all services
>> have started.  Unfortunately in the case of cxf, the Endpoints have all
>> been created by the time I get the
>> ApplicationListener<ContextRefreshedEvent> but the servers may actually
>> still be starting.
>>
>> It would be useful to register a ServerLifeCycleListener which has a new
>> method:
>>
>> void serverCreated(Server server);
>>
>> I could then use this to correlated the corresponding startServer(Server
>> server) events to know exactly when the spring context is "really" ready.
>>
>> I know this is a compatibility issue and wanted to know what other devs
>> thought of the idea and whether its ok if I implement it into 2.7, 3.x and
>> 3.1?
>>
>> Or any alternatives are welcome
>>
>> Currently what I am doing is overriding the ServerLifeCycleManager and
>> intercepting any ManagedEndpoint registrations and sending them onto a
>> custom listener.
>>
>>
>> https://github.com/pellcorp/JavaFirst/blob/cxf27/JavaFirst/src/main/java/com/pellcorp/cxf/DelegateServerLifeCycleManagerImpl.java
>>
>>
>>

--001a1133f1c447234b0518c00778--