Backing the Web Beans Application scope

[pmuir]

Currently we back the Web Beans Application scope with the servlet context, however this isn't sufficient as Servlet may not be available.

The application context should available for the whole time the application is running (including *Web Beans* startup and shutdown), it doesn't need to be replicated and the objects it contains don't support serialization.

So, my proposal is to delegate providing backing for the application context to the AS through the Web Beans bootstrap (https://svn.jboss.org/repos/webbeans/ri/trunk/webbeans-ri-spi/src/main/java/org/jboss/webbeans/bootstrap/api/Bootstrap.java).

This would require the Web Beans bootstrap deployer to have an implementation of BeanStore (https://svn.jboss.org/repos/webbeans/ri/trunk/webbeans-ri-spi/src/main/java/org/jboss/webbeans/context/api/BeanStore.java) which it passes to Web Beans through it's (WB) Bootstrap.

Ales and I had some ideas for how to back it:

• non-serializable JNDI
  
• EJB3.1 singleton
  
• MBean server.
  
  Thoughts?

[alesj]

Ales and I had some ideas for how to back it:

• non-serializable JNDI
  
• EJB3.1 singleton
  
• MBean server.
  
  Thoughts?

As discussed now, I think a plain MC bean is enough.
Perhaps we could only push it into own scoped Kernel/Controller?

[alesj]

"alesj" wrote:

Ales and I had some ideas for how to back it:

• non-serializable JNDI
  
• EJB3.1 singleton
  
• MBean server.
  
  Thoughts?

As discussed now, I think a plain MC bean is enough.
Perhaps we could only push it into own scoped Kernel/Controller?

I mean, for running in MC controller envs.
But I think we could already provide some other impls,
e.g. like the one's stated above.

Other could have their own 'MC',
in GF's case it would be a BundleActivator + boot service.
(I guess we could provide this one as well, for proof of concept)

[pmuir]

"alesj" wrote:
Other could have their own 'MC',
in GF's case it would be a BundleActivator + boot service.
(I guess we could provide this one as well, for proof of concept)

The GF guys are happy to do the GF work I think :-) as long as we provide SPIs they like. This was the only real issue that came up during my meeting with them...

[pmuir]

Notes for Ales to implement:

Before calling Bootstrap.initialize() you need to call Application.setApplicationContext(BeanStore beanStore);

BeanStore is https://svn.jboss.org/repos/webbeans/ri/trunk/webbeans-ri-spi/src/main/java/org/jboss/webbeans/context/api/BeanStore.java - basically a Map<Conextual<?>, Object> with the get, put and remove generified.

Do you want to be notified on shutdown?

[alesj]

Do you want to be notified on shutdown?

How is shutdown triggered?

[alesj]

Before calling Bootstrap.initialize() you need to call Application.setApplicationContext(BeanStore beanStore);

Where do I get this BeanStore from?

[pmuir]

"alesj" wrote:

Do you want to be notified on shutdown?

How is shutdown triggered?

On undeploy of the application.

[pmuir]

"alesj" wrote:

Before calling Bootstrap.initialize() you need to call Application.setApplicationContext(BeanStore beanStore);

Where do I get this BeanStore from?

Good point. I'll write a helper for this in SPI.

[alesj]

"alesj" wrote:

Do you want to be notified on shutdown?

How is shutdown triggered?

On undeploy of the application.

MC will undeploy the bean.
So you should tell me if there is some stop/destroy thing you wanna call.

[pmuir]

So you should tell me if there is some stop/destroy thing you wanna call.

Good point, I was thinking upside down.

I guess we have a bootstrap.shutdown() method. This is semantically a bit odd, but I think it is easier than having some other interface. I'll add that tomorrow/later.