It's not only about starting the container itself. You also need to control the Contexts ;)
LieGrue, strub PS: it's out of question that our documentation currently is not our strongest point :D >________________________________ > From: Harald Wellmann <[email protected]> >To: [email protected] >Sent: Friday, June 22, 2012 8:18 PM >Subject: Re: Booting in Java SE? > >Hi Mark, > >Quoting from your blog: > ><quote> >Have you ever tried to boot a CDI container like JBoss Weld or Apache >OpenWebBeans in Java SE? While doing this task you will end up knee deep >in the implementation code of the container you are using! ></quote> > >Well, I've never had any trouble using > > new Weld().initialize(); > >that's simple enough and documented, so where's the problem? > >Only with OWB I'm currently knee-deep in source code, for lack of decent >documentation.... > >Deltaspike as another wrapper doesn't help understanding the underlying >containers, either. > >Of course, it's nice to have such an abstraction, but I think this >should really be part of the official CDI API. > >I believe there's a CDI spec JIRA issue on this topic - is there any >progress for CDI 1.1? > >Best regards, >Harald > > > >Am 22.06.2012 19:46, schrieb Mark Struberg: >> Hi Harald! >> >> >> Those days I recommend to use DeltaSpike cdictrl [1]. The work is based on >> the stuff we did in OWB cdi-test, but we also added implementations not only >> for OpenWebBeans, but also for JBoss Weld and Apache TomEE. Others might >> follow ;) >> >> >> I also wrote a small blog about it recently [2][3]. >> >> >> LieGrue, >> strub >> >> >> [1] >> https://cwiki.apache.org/confluence/display/DeltaSpike/Temporary+Documentation#TemporaryDocumentation-WithJavaSE >> [2] >> http://struberg.wordpress.com/2012/03/17/controlling-cdi-containers-in-se-and-ee/ >> [3] >> http://struberg.wordpress.com/2012/03/27/unit-testing-strategies-for-cdi-based-projects/ >> > > >
