Actually, on second thought startAsync should not be necessary. It
already happens in the WarDeploymentProcessor.
Thanks for spotting this - I'll run a few tests with this removed.
cheers
-thomas
On 07/20/2012 10:19 PM, Thomas Diesler wrote:
Does it not say this?
/**
* Start the web context asynchronously.
* This would happen during normal WAR deployment
*/
public synchronized void startAsync() {
/**
* Start the web context synchronously.
* This would happen when an OSGi Web Application Bundle (WAB)
transitions to {@link Bundle#ACTIVE}
* i.e. the WAB starts
*/
public synchronized boolean start(long timeout, TimeUnit unit)
throws TimeoutException {
On 07/20/2012 07:38 PM, David Bosschaert wrote:
> Hi all,
>
> While looking at the WebContextActivationProcessor [1] I see that the
> ContextActivator can get started in 2 places: in the deploy() method and
> in the LifecycleInterceptor.
> I'd like to understand when each of these are used? Is it not possible
> to do this in a single place?
>
> Thanks,
>
> David
>
> [1]
>
https://github.com/bosschaert/jboss-as/blob/master/osgi/web/src/main/java...
>
> _______________________________________________
> jboss-osgi-dev mailing list
> jboss-osgi-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-osgi-dev
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx