"alesj" wrote : "pete.muir(a)jboss.org" 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)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212398#4212398
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212398
At the moment there's provisions for deploying other JCA providers (like BouncyCastle) though I'm not sure I can/should keep that (the JDK has its own provider deployment mechanism and there isn't a great way to make them play together that I can see). As for providing alternate implementations, I do not have any plans to do so at this time, though these services can work with any provider implementation.
I chose the name because all these provided services relate specifically to cryptography, so it seems to make sense to me.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212395#4212395
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212395