Oki, that seems to be a bit more work to be left still.

I'd then suggest to go on with the immanent features and release OWB-2.0.1 
pretty soon while targetting 2.0.2 for the SE work.

txs and LieGrue,
strub


> Am 15.08.2017 um 13:48 schrieb John D. Ament <johndam...@apache.org>:
> 
> Mark,
> 
> SE support is still a long ways from being done.  Most of the issues are
> resolved, all of the remaining problems are related to OWB not honoring
> when the container's been shutdown.
> 
> The good news, by removing the automatic starting of request context and
> properly shutting down app context in the SELifeCycle class, OWB is finally
> marking the proxies as invalid, but it seems like we still need to add an
> isRunning check somewhere.
> 
> John
> 
> On Tue, Aug 15, 2017 at 7:19 AM Mark Struberg <strub...@yahoo.de.invalid>
> wrote:
> 
>> Hi folks!
>> 
>> I'd love to fix OWB-1209 and get Johns SE changes in.
>> I think we are then ready to roll a 2.0.1 release, isn't?
>> 
>> John, I'll be available on IRC to coordinate and review your proposed SE
>> changes.
>> Of course we could also discuss it via IRC, but might be easier to give
>> that feedback via a shared hangout screen.
>> 
>> LieGrue,
>> strub
>> .
>> 

Reply via email to